Guidelines for GitHub use
Repository Naming Conventions
Consolidating to single organizations introduces naming competition and potential namespace collisions. Please name every repository to clearly communicate ownership, readability, and consistency within the organization. We propose everyone conform to the following convention when naming repositories:
- The repository name should use all lowercase letters
- Separate words using dashes (-)
- The first word should describe your college or division, such as your 4-letter abbreviation (i.e.
- The second (or more) word(s) should describe your working group, such as department or research lab (i.e.
- Use the rest of the name to describe the repository with high specificity (i.e.
GitHub Enterprise has three levels of repository visibility:
- Public repositories are visible to the internet.
- Internal repositories are visible to members of the Enterprise (anyone with a Texas A&M NetID).
- Private repositories are only visible to those with direct access.
The student organization allows repositories of any visibility level.
The institutional organization allows new repositories at any visibility level. Changes to existing repositories from
public will be blocked and reverted. The owner of a private repository can submit a ticket or pull request to grant their visibility change.
Using Git and GitHub
If you are new to Git or GitHub, the Get Started with GitHub guide is a great place to start. More advanced users are encouraged to check out the documentation for the advanced features at GitHub Docs.
Some additional resources to learn Git and GitHub:
- About Git - Learn about the version control system, Git, and how it works with GitHub.
- GitHub Hello World - A real example of how to use GitHub.
- The GitHub Flow - Understand how best to collaborate on projects.
- GitHub Guides Index
- GitHub CLI Tools and GitHub CLI Documentation
- Build Your Own Octocat