-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activity 1: History #1
Comments
6810
All merges tied to issues since we squash and merge. Each commit represents a pull request.
😬 |
|
12356, but not full history, history has been squash when including it from svn to git
yes, merges, maven release message
legacy project, multi team with no proceesse ... not really :p |
|
How many commits have been made on your repository? |
How many commits have been made on your repository? Do you find any patterns? |
8625
We're following the pattern where each commit that gets merged into main branch encompasses the number of ticket in Jira and its title.
We have some checkups in place which verify the commit message pattern and it will disallow commits from being merged if they break that pattern. |
How many commits have been made on your repository? |
Duration: 10 minutes
History of your repository
Let's look at the history of your repository. Using a command line tool, run the following command on it:
Be sure you are in the location of that file inside your command line tool.
Explore a commit
Choose a commit in your repositories history and let's explore that single commit. Run the following command to see the details of the commit.
Be sure you are in the location of that file inside your command line tool.
How many changeset are in your repository
Let's find out how many changes your repository has. Run the following command to see how may commits have been made in your repository:
Be sure you are in the location of that file inside your command line tool.
Report out
Report your findings in comments section below:
For examples and more information, please see README.md -> Activity 1.
The text was updated successfully, but these errors were encountered: