- Notifications
You must be signed in to change notification settings - Fork13
A painless Git setup with an easy way to share Git configs and scripts within a company using GitHub Enterprise.
License
Autodesk/enterprise-config-for-git
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
A painless Git setup with an easy way to share Git configs and scripts within a company using GitHub Enterprise.
Enterprise Config for Git adds a new Git setup command (e.g.git mycompany) to your Git config (via Git config alias) that configures a developer machine. The setup command checks the installed Git version, ensures Git LFS is installed properly, configures the user name and email based on the GitHub Enterprise profile, and configures the Git credential helper with a GitHub Enterprise token. It also adds an easy way to distribute company Git configs (e.g.Git push protection) and Git helper scripts (e.g.git adsk clone).
Enterprise Config for Git supports Windows, Mac and Linux and a great number of shells such as BASH, ZSH, DASH, cmd.exe, and PowerShell.
Please find more details aboutEnterprise Config for Git in the corresponding Git Merge 2016 talk (slides).
In order to useEnterprise Config for Git you need to fork it to your GitHub Enterprise instance and adjust it for your company:
- Define thename of the setup command for your company
- Set theGitHub Enterprise server (e.g.
github.mycompany.com) - SetEnterprise Config for Gitorganization/repository of your fork on your GitHub Enterprise server (e.g.
tools/enterprise-config). Please ensure every engineer has read access. - Define yourcontact in case of errors
- Register anOAuth application on your GitHub Enterprise server and setup theEnterprise Config for Gitclient ID and secret.
- Configure your desiredcompany email pattern.
- Create a production branch based on the master branch.
git clone --branch production <<YOUR ENTERPRISE CONFIG URL>> ~/.enterprisegit config --global include.path ~/.enterprise/config.includegit <<YOUR SETUP COMMAND>>Any Git config you define inconfig.include will be distributed to all your engineers with the setup command. Plus you can add shell scripts to the root directory ofEnterprise Config for Git that are available to all engineers via the setup command (see theclone.sh implementation as example forgit adsk clone)
Enterprise Config for Git is a fairly new project and not very mature at this point. In case of trouble or questions please create a GitHub issue and we will try to get back to you ASAP.
About
A painless Git setup with an easy way to share Git configs and scripts within a company using GitHub Enterprise.
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Contributors3
Uh oh!
There was an error while loading.Please reload this page.