My workflow is typical: create a feature branch from main/master, raise a PR when ticket is complete, and maintain a separate release branch for production depl

My workflow is typical: create a feature branch from main/master, raise a PR when ticket is complete, and maintain a separate release branch for production deployments. I use rebase instead of merge so the commit history doesn't get cluttered with merge commits. Pain points: -coming up with good commit messages -including the story ticket number in the branch name and commit message