Activity 1: History
selkins13 opened this issue · 8 comments
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:
git log --oneline
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.
git log --pretty=fuller [commit hash]
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:
git log --oneline | wc -l
Be sure you are in the location of that file inside your command line tool.
Report out
Report your findings in comments section below:
- Include answers to the following questions in your comments:
- How many commits have been made on your repository?
- Do you find any patterns?
- Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
⚠️ Make sure during all this exercise you don't post any private information that should not be shared publicly.
For examples and more information, please see README.md -> Activity 1.
How many commits have been made on your repository?
6810
Do you find any patterns?
All merges tied to issues since we squash and merge. Each commit represents a pull request.
Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
😬
Not really but we tie them back to issues that have more details.
How many commits have been made on your repository?
85
Do you find any patterns?
majority of commits are PR merges
Are the commit messages relevant enough
Most of them (except for merges)
How many commits have been made on your repository?
12356, but not full history, history has been squash when including it from svn to git
Do you find any patterns?
yes, merges, maven release message
Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
legacy project, multi team with no proceesse ... not really :p
- How many commits have been made on your repository?
6682 - Do you find any patterns?
Many dependency upgrades and merge commits - Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
Mostly yes. There are a few here and there that do not really follow the standards
How many commits have been made on your repository?
7283
Do you find any patterns?
Bug fix
Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
Yes
How many commits have been made on your repository?
119003 commits
Do you find any patterns?
all our commit messages contains jira id to link code change to the actual issue or story
and quite a lot of merge request commit
How many commits have been made on your repository?
8625
Do you find any patterns?
We're following the pattern where each commit that gets merged into main branch encompasses the number of ticket in Jira and its title.
Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
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?
397
Do you find any patterns?
Merge, bug fix
Are the commit messages relevant enough to know why the file changed? Do you follow a standard?
Yes