I'm with @kerimovkhikmet here. I was about to post the same example as @e.langelaar, because I use that to in my OSS account. My bots have a bit more scope than they should in hindsight, but I'm not in a corporate production environment (not really an excuse, just pointing out I probably should tighten that up).
Timothy Stone (7c13a009) at 02 Feb 02:22
Timothy Stone (a87fd9f4) at 02 Feb 02:22
ci: add bash template from TBC
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
ci/add-bash ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
bash tooling for gitlab pipelines.
Timothy Stone (f780c82f) at 02 Feb 02:20
ci: correct quoting
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
ci/add-bash ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
bash tooling for gitlab pipelines.
Timothy Stone (f1b83737) at 02 Feb 02:16
ci: add bash template from TBC
Timothy Stone (42729779) at 02 Feb 02:09
Timothy Stone (42729779) at 02 Feb 02:09
docs: update documentation and branding
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
docs/template-updates ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
Add portable logo and update Contributing and Readme documentation.
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
docs/template-updates ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
Add portable logo and update Contributing and Readme documentation.
Timothy Stone (42729779) at 02 Feb 02:07
docs: update documentation and branding
Timothy Stone (a92d0ff2) at 02 Feb 01:30
Timothy Stone (584ba94f) at 02 Feb 01:30
chore(deps): update template packages and dependencies
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
chore/deps ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
Update TBC SemRel to v4+. Update devDependencies to current versions.
Sonar changes are common in some projects. Add a scope for highlighting changes to address Sonar findings.
The MR originates from a topic/feature/bugfix branch. Do NOT open an MR from your master or main.
chore/deps ... this SHOULD NOT be master or main.
The MR subject or squashed commit message subject follows Conventional Commits.
The work MUST not fail code style/linting or existing and new unit tests.
Update TBC SemRel to v4+. Update devDependencies to current versions.
Sonar changes are common in some projects. Add a scope for highlighting changes to address Sonar findings.
Timothy Stone (a92d0ff2) at 02 Feb 01:28
chore(deps): update template packages and dependencies
Timothy Stone (59930c23) at 02 Feb 01:20
chore(deps): update template packages and dependencies