commit-message | quick little macOS utility to make writing commit messages

Assuming I have a pom.xml containing a parent dependency like this:

I'm trying to get started using semantic commit messages according to the Angular convention https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#

But still can't find the right commit type when installing a new dependency in my project. In the end, it should end up like : install storybook. What type should I use?

I've been wondering is it possible to change the message that appears in the input field when you commit on Github. Refer to the picture below:

I like my commits to be as descriptive as possible and enjoyable to read. I want Github to suggest 📝 Create README instead of Create README.md.

When I search for the solution, the 'google search' shows irrelevant answers. Is it somehow possible?

Note: This does not answer my question.

I have a static blog setup and every time I want a new post I have to commit and push a .md file. This is part of a group, so I was wondering if there is a way to automate the commit and push part every time a new .md file is saved to a google drive folder.

The first part is covered by IFTTT, where every time a new file is uploaded, a new issue is created on github containing the link to the file in the body.

However, I don't know how to create the action that will now download the file, create a new branch, commit and push the file to that branch and finally set up a pull request for me to approve.

If you know of any other way of automating this process I am open to suggestions!

Thanks!

Edit1:

I am not really sure how to complete this (including generating a random number where I wrote . Here's what I have so far:

I have a declarative pipeline that uses a kubernetes agent.

I have two GitHub Actions in the same repo. I'm trying to update one from the other, but I get the following error when trying to commit and push the changes:

! [remote rejected] HEAD -> some-branch (refusing to allow a GitHub App to create or update workflow .github/workflows/the-other-action.yml without workflows permission)

This is a simplified version of the GH Action I'm trying to run:

I am creating a script to do a Pull request using the below Azure CLI script.

az repos pr create --description $PR_Description --merge-commit-message $PR_WorkItemNo --org $orgname --source-branch $PatchName --target-branch "main" --title $PR_Title --project $projectname --repository $PR_repository --work-items $linkedworkitemno

Assigning a single work item (eg "72076") to this variable $linkedworkitemno - works fine and associates the single work item to the PR.

But when I add two work items with space (eg "72076 72126") - as explained in MS Docs (- --work-items - IDs of the work items to link to the new pull request. Space separated https://docs.microsoft.com/en-us/cli/azure/repos/pr?view=azure-cli-latest#az_repos_pr_create), it is not linking both items to the PR and only associates the FIRST work item.

can you please help me with this query?

I have an angular project where I want to enforce conventional commits. I have not been able to successfully had the right hook to prevent incorrect hooks.

I started with this tutorial, where it said to add the following to package.json:

In a company, we have a project that we are working on for some time already. In this project we use git for versioning. We are trying to make our git workflow more professional and more easy to collaborate. One of the steps we want to take is automatically generate a changelog, e.g. with generate-changelog. This package requires that the commits our formatted following the Angular commit message format.

I will be happy to write all the commits in the future following this format, but we still have a lot (a couple of hundreds) of commits that do not follow this format. In the meanwhile, I want to have the changelog generated automatically.

Is there a way to generate the changelog automatically, although old commit messages do not follow the required format? Or could we possibly 'update' the commit message such that we do follow the required format?

In case you need more info, let me know and I will update the question accordingly.

Update: I want to prepend all old commit messages with some text like: docs:. Interactive rebase as suggested here and in the answer below does work, but only if you have a few commit messages. I am looking for a way to change all commit messages at once. An exmaple that I did not get to work yet can be found in this SO question/answer.