A couple years ago I created a C# program for one of my classes. We had to work in groups and used GitHub. Now that I finally graduated I'm trying to add some code to my GitHub account to show to prospective employers, I realized that that program is not in my repositories (another teammate created it, but I contributed). Also, we have a lot of useless files in that repository and everything is a mess, it doesn't even has a Read Me.
So, my question is: should I create another repository without the useless files and cleaner code? Or should I fork the repository? What would be the best way to add it to my profile?
Also, what book, video, website, etc. would you recommend to learn how to use GitHub fast?
if you fork the repository people will see that you forked from a repository and there will be a history of commits made by whoever committed into that repository.
Assuming that it is not a very large code base, why don't you just create a new repository and just start doing the project again in a progressive manner where you can demonstrated your skills on the project. I am assuming as you already done the project early it will be easier for you to create the project ground up and will give you a chance to improve the previous code along the way.
you can find lots of git hub tutorials for beginners if you just search on google.
try git
I find this is very useful git scm
git for begginers
Related
We are a small team doing our own project and we need to somehow add a repository to each participant, so that later we can show what we did, how can this be done correctly?
We tried to google but did not really understand how to do it, leaving just a link like 'I took part in this project' seems to us not such a right decision
You need to set up a central, bare repository and have everyone clone that. Then they push and pull from that central repository to stay coordinated. There are various workflows of which the feature branch workflow is a good place to start.
Rather than doing this yourself, it's much simpler to host your code on a service such as Gitlab or Github. Both offer private repositories for free and many, many excellent additional features.
I want to move the entire project board of a GitHub repository to another. Is there any way that can be done without manually copying each and every card.
Project board is a feature on GitHub to organize and prioritize work. More
Thank you.
EDIT:
When I contacted GitHub Support, I got the following response.
There isn't currently a way to merge a Project on GitHub, but I can
definitely see how that would be useful. I can't make any promises but
I'll let the team know you'd like to see us add this feature in the
future.
Hello I'm new to Github/Gist and I want to use this code, but I need to modify it a little bit. Can i just fork this code and modify it to use it for my own projects? Or do i have to link to the author etc.? Here is the link: https://gist.github.com/learncodeacademy/777349747d8382bfb722
Thank you!
Github repositories are meant to be forked. You don't have to ask an author for permission. Anyway, the gist you linked to has already been forked 30 times.
When you are using a forked repository.It shows up as "forked from xyz". So attribution is automatic. But if you want to, you can always give an extra credit to the author by mentioning it specifically.
Forking a repository on Github, creates an individual copy of the code. This feature is meant to encourage collaboration as well as allow you to experiment with the repositories code. Forking can be used to propose new changes to someone else's code or jumpstart an idea or a new project. As the repository was created by someone else, it is always important to understand the limitations of using their code for your own projects (especially if you plan on selling this product). Every repository created on Github has the chance to create a license file. This file will tell you what you can or cannot do with the forked code. Often open source code is meant to be used and shared with everyone, but it is still good to check. Here is Githubs documentation on forking repositories: https://help.github.com/articles/fork-a-repo/. For more information on licensing files see http://choosealicense.com/. Github gists follow the same standard. If you are still worried, it does not hurt to contact the owner of the repository and verify that you can use it for your own projects.
The point of open sourcing code on GitHub is for others to take and use for themselves and learn from it. Also, like fuchsteufelswild said, when forking on GitHub it automatically gives credit to the author so you should be good.
I've assumed maintainership for a given project on github. I've done so by cloning the repository of the original authors and pushing my own changes and developments. This was done in accord with the original authors, so they do not expect to work on this in the future. Nevertheless, my repository is marked as a fork of theirs, which makes it appear less official. Is there some way to denote a given repository as official? To swap the relation between my repository and that of the original developers?
I guess I could delete my repository, then ask the original devs to transfer theirs to mine, then let the original devs fork from that, then push my own changes from my local repo. But somehow this feels wrong. It would rely on my local copy. Migration of e.g. the pages branch might be causing extra trouble. I hope there is a cleaner solution.
There doesn't seem to be a clean way to do this.
It seems your best option is to ask GitHub support to convert your repository to "normal mode" as opposed to "forked from" mode.
Another solution is to delete and recreate the repository. However, this can be dangerous, as the wiki and issues data will also be deleted in this process.
If you have further questions about this then let me know in comments and I can amend my answer.
We have a fairly large project, and I've decided that Google Code is not quite living up to expectations. Github looks like a much more suitable platform -- but I feel like there's no escape for us. Is it a case of migrating stuff over manually? We're using svn currently, so I understand that we'll need to move to git somehow - is this going to be possible considering that I don't have admin access to our repository? Also, I know this is subjective and I don't want to start a holy war, but please also comment on your feelings about Google Code vs Github. Should we also be considering SourceForge?
I've used all, and now I am using github and I am completely satisfied. Sourceforge had annoying ads and was slow, google code didn't have the features I wanted/needed.
As for moving to github, they have a guide here, the process should be quite simple:
http://help.github.com/svn-importing/
We're using svn currently, so I understand that we'll need to move to git somehow - is this going to be possible considering that I don't have admin access to our repository?
Nope, you can use git svn to convert a repo, even if you don't have admin access. Here's a good tutorial (from one of the GitHub guys, no doubt) that explains how to convert an SVN repo to Git (including how to migrate tags and branches properly, which git-svn doesn't do very well).
but please also comment on your feelings about Google Code vs Github.
I've never used Google Code for personal projects. I know from a visitor's standpoint, I like the interface and tools used by GitHub a lot better.
Should we also be considering SourceForge?
Ugh... I personally think SourceForge is probably the worst of the free source code hosting facilities nowadays.
I think before you go through all the work to migrate to github (which is great yes) I would consider what your problem actually is. If it is just that you are using svn and that is not a distributed version control system you could just migrate your google code repository to be HG (Mercurial) based and you would get all the benefits of a distributed version control system but could otherwise stay at google code (which has great features that github does not have as well..)
Google announced today that they're closing Google Code. They added a migration tool to export projects to GitHub, it just takes one click.