Adding a Mentor as a Collaborator to the Repository
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.
Unlock now
While we are on GitHub, let’s add our mentor to our repository.
In the GitHub menu bar, click the ⚙ Settings button. It is the last button on the right.
A list of options is displayed on the left side of the screen. Under Access (top left under General), click Collaborators. You may be required to log in.
On the Collaborators and teams page, you will see a section called Manage access. Click the Add People button.
A dialog will appear where you can provide your Mentor’s GitHub username, full name, or email. You will be able to find all three of these items in your bootcamp documentation.
Once you enter either of the items, you should see a card with the full name and username of the Mentor. If you do not see this, you may have entered it incorrectly. Click the card to continue.
You will now be given a green Add Mentor’s Name button. Click the button to continue.
What we have done.
- Added a mentor to the repository
At this point you are ready to complete the assignment.
Commit Early and Commit Often
As you work on your assignments throughout the week, make it a habit to commit your changes frequently - ideally every time you complete a small feature, fix a bug, or reach a logical stopping point in your work. Think of commits as save points in a video game: they create snapshots of your progress that you can always return to if something goes wrong. Frequent commits provide several important benefits: they create a detailed history of your problem-solving process (which mentors find valuable when reviewing your work), they make it easier to identify exactly when and where issues were introduced if your code stops working, and they ensure you never lose more than a small amount of work if your computer crashes or you accidentally delete something. A good rule of thumb is to commit whenever you’ve made progress that you wouldn’t want to recreate from scratch - this might be every 30 minutes to an hour of productive coding. Remember, there’s no such thing as too many commits, but there is definitely such a thing as too few. Your future self will thank you when you can easily track down that working version from yesterday instead of starting over from scratch.