### Problem to solve Committing changes to code can create consequent effects, which can be detailed and managed via issues. Creating such issues directly (TODO issues) via commit messages would be a friction reducing feature, and a improvement to the development workflow. My own use case involves documentation updates (detailed below in [Further Details](### Further Details)) but I believe the use case extends further. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Further details > Writing good documentation is the sign of a good developer. *Maintaining* good documentation is the sign of a saint. You've been working hard on fixing a bug, or implementing a new feature. Finally after 4 hours, it works! And better yet, Gitlab's CI tooling tells you that all your tests have passed. So you immediately sit down and update your project's documentation, right? Well, let's be honest: not all of us are saints. Documentation often drifts away from our project's current state. ### Proposal Add support for automatically raising issues via commit messages. * Example using inference: `feat: add monkey handler, needs docs` * Example using quick action: `feat: add monkey handler, /todo add monkey handler docs` ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references Raised on twitter: https://twitter.com/tmthyrd/status/1199316276348407808