backend-refactor-test-runner-docker-image
Squashing
We squash commits on a branch before merging because we want a single commit with a correctly formatted commit message.
Do the following on your local machine to squash the commits. The commands are shown as running from the root of the project, but they can be run from anywhere.
-
Use the Code button above to get the Step 1 commands to check out the branch locally.
-
Run the following command to squash the commits on your feature branch.
commands/premerge-squash.sh -
When your editor opens, write a multi-line commit message formatted correctly as a conventional commit.
An example of a conventional commit is given below.
type: message Co-authored-by: First1 Last1 <email1@example.com> Co-authored-by: First2 Last2 <email2@example.com> Closes #<issue-number>Here are some common types.
-
feat:- A commit that adds new functionality from the client's perspective. -
fix:- A commit that fixes a bug in existing functionality from the client's perspective. -
refactor:- A change to production code that add new functionality or fix a bug from the client's perspective. However, it may remove functionality (which should have an exclamation pointrefactor!:). Typically used to redesign product code to make it easier to add more functionality or improve performance in the future, or to make the code more readable and understandable. -
docs:- A change in the documentation or documentation system. -
build:- A change in the build system. -
test:- A change in a test or the test system. -
ci:- A change in the continuous integration and delivery/deployment system. -
chore:- A task performed to maintain the system. E.g., bumping the version number of the product. Upgrading the version of a dependency. These changes do not improve anything, but must be done as part of normal operation.
The definition of "client" depends on the project. For the API project, its clients are Frontend and Backend. For the Frontend, its clients are people who use the frontend.
-
-
Save the commit message and close your editor.
-
Run the following command to push your squash commit to GitLab.
git push --force origin $(git branch --show-current)
Closes #47 (closed)
Merge Request-Berichte
Aktivität
added StatusSprint Backlog label
assigned to @mbryan3
🦙 MegaLinter status:
Descriptor Linter Files Fixed Errors Elapsed time 
bash-exec 8 1 0.03s shellcheck 8 6 0.17s shfmt 8 7 0.03s jscpd yes 2 1.78s 
hadolint 3 0 0.12s eslint 19 1 0.62s standard 19 1 4.28s eslint-plugin-jsonc 5 0 1.65s jsonlint 5 1 0.17s prettier 5 1 1.02s v8r 5 0 8.79s markdownlint 15 58 0.52s markdown-link-check 15 1 8.95s markdown-table-formatter 15 0 0.29s spectral 1 1 2.47s checkov yes 3 13.73s devskim yes 5 1.04s dustilock yes no 5.22s gitleaks yes no 0.5s git_diff yes no 0.02s secretlint yes no 1.36s syft yes no 0.57s trivy yes 1 5.97s cspell 62 206 19.4s misspell 61 1 0.1s prettier 5 1 0.75s v8r 5 0 4.57s yamllint 5 1 0.4s See detailed report in MegaLinter reports
You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:
- oxsecurity/megalinter/flavors/javascript@v6.22.2 (57 linters)
MegaLinter is graciously provided by
Bearbeitet bei Ghost Usermentioned in commit b5c58ca5
mentioned in issue #48 (closed)
The release is available on:
v2.0.0- GitLab release
Your semantic-release bot
