You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use semanic branchnames like: feature/PROJECT-123-a-nice-new-feature or bug/PROJECT-456-oh-no-a-bug that will contain the Project ID and its Ticket Number.
The Project ID and Ticket-number are also referenced in the Commits, making it easy to link them in the Ticket. So a commit would look like the following:
PROJECT-123
chore(package.json) updates some dependencies.
feat(src/components/someComponent.tsx) Implement awesome feature
It would be nice to be able to do that with opencommit
The text was updated successfully, but these errors were encountered:
We use semanic branchnames like:
feature/PROJECT-123-a-nice-new-feature
orbug/PROJECT-456-oh-no-a-bug
that will contain the Project ID and its Ticket Number.The Project ID and Ticket-number are also referenced in the Commits, making it easy to link them in the Ticket. So a commit would look like the following:
It would be nice to be able to do that with opencommit
The text was updated successfully, but these errors were encountered: