Accelerate velocity and increase productivity by connecting your GitHub Enterprise account to Waydev
The GitHub Enterprise integration enables us to provide reports that help you in:
For daily stand-ups, Waydev integrates with GitHub Enterprise to provide you with:
For one-on-ones, Waydev integrates with GitHub Enterprise to help you with:
For code review, Waydev integrates with GitHub Enterprise to provide you with:
For monthly and quarterly reports, Waydev integrates with GitHub Enterprise to help you with:
Step 1: After you create a Waydev account, you will need to select a Git provider. Select GitHub Enterprise.
Step 2: Navigate to GitHub Enterprise and create an access token.
Step 3: In the upper-right corner of any page, click your profile photo, then click Settings.
Step 4: In the left sidebar, click Developer settings.
Step 5: In the left sidebar, click Personal access tokens.
Step 6: Click Generate new token. Select the scopes, or permissions, you’d like to grant this token. To use your token to access repositories from the command line, select repo.
Step 7: Navigate back to Waydev and insert the following:
Step 8: You will be directed to the Repositories page, where you will need to select the repos you wish to import. After you select the repos, click Save Project. You have connected your GitHub Enterprise account successfully!
GitHub Enterprise is the on-premises version of GitHub. GitHub Enterprise includes the same set of features as GitHub but it is packaged for running on your organization’s local network. All repository data is stored on machines that you control, and access is integrated with your organization’s authentication system (LDAP, SAML, or CAS).
GitHub Enterprise also includes support for pre-receive hooks, a tool that can help you enforce critical business rules, meet compliance requirements, and help prevent other undesired changes from ever being made. GitHub Enterprise is recommended when you need complete control over repository and project information.
Three important terms used by developers in GitHub are fork, pull request, and merge. A fork, also known as a branch, is simply a repository that has been copied from one member’s account to another member’s account. Forks and branches allow a developer to make modifications without affecting the original code.
If the developer would like to share the modifications, they can send a pull request to the owner of the original repository. If, after reviewing the modifications, the original owner would like to pull the modifications into the repository, they can accept the modifications and merge them with the original repository. Commits are, by default, all retained and interleaved onto the master project, or can be combined into a simpler merge via commit squashing.
A repository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets – anything your project needs.
Branching is the way to work on different versions of a repository at one time. By default your repository has one branch named master which is considered to be the definitive branch. We use branches to experiment and make edits before committing them to master.
When you create a branch off the master branch, you’re making a copy, or snapshot, of master as it was at that point in time. If someone else made changes to the master branch while you were working on your branch, you could pull in those updates.
In GitHub, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes, so other contributors can understand what you’ve done and why.
Ready to improve your teams' performance?