Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm working in a command which uses a private repository at GitHub. This is a contract work and once it's finished, I won't have access to this repository anymore.
I commit there quite often and, therefore my "Your Contributions" (GitHub's "timeline" or " Summary of Pull Requests, issues opened and commits") looks pretty good. I want it to remain look the same.
But nonetheless, when the job finishes and I won't have access to this repository (the admin restrict access for me to this repository), I'm almost sure my "timeline" will become more gray immediately, since this repository is deleted from the list of the repositories I can contribute to.
Isn't that so and how do I avoid this?
UPDATE:
The reason I want to avoid it is that I want the potential employees to be able to see how I work by looking at my timeline.
Re-stating the problem briefly, once your account is removed as a contributor, your contributions don't show up in the same way they currently do. You want people staying on the project to still see your contributions as a model of how they should be committing.
Once you are finished, get them to create a dummy GitHub account for you. This account will remain a collaborator, but you won't be able to access it. You can then re-write the commit history to make it seem like the dummy account made all of your commits. The history will look the same, but you won't have access to the dummy account - or their repo.
There is plenty of good information on how to do this: see e.g. Git, rewrite previous commit usernames and emails or you could try https://github.com/davidfokkema/git-rewrite-author
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
What is the difference between GitHub and Bitbuck source repositories? Which one is better if I want to share source code privately?
Bitbucket just provides you unlimited git private repositories for free for a five users plan. As they say Bitbucket is the Git solution for professional teams. In GitHub if you require private git repos then you have to purchase a plan for it. The two services have very different billing structures, for example -- GitHub charges per private repo, BitBucket charges per private collaborator.
Also, their issue tracking, wiki, history viewer and collaboration features work pretty differently. GitHub has its own bug tracking system and BitBucket provides JIRA integration.
This image provides the difference in short:
Answer to you question: Which one is better if I want to share source code privately?
If you don't have many collaborators to add (not more than five) then BitBucket is the best to choose as you will get a free private repo. If you have many collaborators to add on the project then GitHub charges for the repository instead of the number of collaborators.
The rest depends on you to choose what features you require and you may choose according to that.
Source of Image: https://www.upguard.com/articles/github-vs-bitbucket
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I need to keep a revision system of changes. My question isn't the structure but the behavior.
For example, let's say you are working on a webpage in a code editor. How often would you make a revision for the developer as he's coding the page? Do you save when he saves? Do you save every hour? How many revisions should you keep?
What behavior would you expect in this scenario?
Update:
It seems that it makes a difference if the content is saved online versus saved locally. In my project it's saved online like, WordPress posts or Google docs. I can save locally to the cache or even to a directory on the users computer if they use the desktop software.
When you are versioning, you:
make sure that teammates will not override each-other's work
write a version diary for future use to be able to handle any scenario
Since it is possible that at some remote time in the future you will need to roll back, it is better to make sure that upon looking at the commit messages, you will be able to determine easier where to roll back. Also, commit messages are helping your teammates to determine what did you do. As a result, my advice is that you should make a commit whenever you have completed a small part of your work, so your commits should be atomic and their message should be speaking for themselves.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I found an interesting project on GitHub (a PHP Library) and I'm currently working on improving it.
I'm making big changes in the guy project. I'm changing the lib's architecture, fixing some bugs, adding some features, refactoring...
Since the changes are big, I don't plan to make a pull request for the guy to push my changes to his repo.
So here's my question: Should I fork his repo, delete everything in it and push "my" code, or create a new repo and just make a link in the Readme informing people that this project is based on the guy's one?
You are referring to the original meaning of a fork:
a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct piece of software
If your changes are so different from the original codebase, then your second option looks ok: new repo, and reference to the old one in the README.
A "GitHub fork" really makes sense when you want to collaborate back to the original repo.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
When using GitHub to host a repository, can I use it for free (without having to pay for private repos), yet protect my work so others cannot edit it?
Can I essentially have it read-only?
On GitHub, others cannot edit your work, they can copy it (clone or fork) and then send it back to you - it's then your job to accept the code they submit and only if you want to.
If you wish to hide what you are doing, aka have a private repository (still for free), may I suggest using Bitbucket or GitLab.
For good tutorials and ressources for Git and GitHub, I'd suggest the following:
The Pro-Git book by Scott Chacon available on the git website.
The Try Git website available on GitHub made by CodeSchool
Or you can try the Git Immersion
If you're still hungry after this, there is a good list of other git stuff here.
Have a great time learning Git ;)
Nobody can directly edit your work on Github, though they can fork your public repos and make changes (to your code) there.
The only way their edits will appear in your code is if you accept the pull request from the fork.
Resources:
Github Help
Git SCM
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have created a GitHub account.
I'd like to know how to use it and why is should be used.
GitHub hosts git repositories. Git is a Distributed Revision Control System which allows you to store source code (or other data) in a versioned repository, and then (if you so desire) share that information and collaborate with other people.
A good free book to get started with using Git is ProGit ( http://progit.org/book/ )
GitHub hosts Git repositories in such a way that it combines a social networking type site with a programming site to create a social programming site. You can just push your git repos up to GitHub to share your code with the world.
http://try.github.com/levels/1/challenges/1
I was just viewing a git hub tutorial today! Git Hub on code school. You may have to sign up for a free account. I stopped about halfway through because its going to be awhile before I need git hub, but I feel like I learned some stuff.
Are you using a mac? There is a git hub app. http://mac.github.com/ I can't say anything about it though.