- What are you seeing, and how does it differ from what you expect to see?
In our company, we started using
squash commit in our merge requests. Before, we had a pipeline that checked for validity of commit messages. (length & containing issue number). Now using
squash commits on Git lab merge requests, we are able to provide custom commit message, but we cannot monitor it.
- What version are you on (Hint:
/help) ? and are you using self-managed or gitlab.com?
Self-Managed, Community-Edition 13.0.3
I believe it helps if there was an
ENVIRONMENT_VARIABLE set for custom squash commit message that user has entered , so we can inspect it and check it in our CI/CD process.
It would be helpful too, if there was an option to enforce squash commit message and description be taken from merge request’s title and description.