In our current project, it is like feature/123-brief-feature-name If it is a bug, it usually is bug/123. 123 represents the ticket number.
Would love to hear what everyone else is using
I prefer feature/<JIRA_No> , bugfix/<JIRA>, hotfix/<> so on
EmployeeId_JIRA-NO/INCIDENT-NO/<RandomFixName>
we have JIRA_NO-<your-branch-name> where jira no will open jira when clicked and we have some release pipeline that checks if that particular JIRA is merged or not if it is not, release won't happen.
<Project Name>-<Ticket No.>-<Few words so I remember while switching>
Jira ticket number that's it
<jira_no>-watever
We use Linear for task management, and Linear provides branch names which we use
Ah, naming. The hardest task in all of programming!
fb_<meri-marzi>
Today while working I had an epiphany, a sudden spark of ingenuity. Versioning filenames like the fast and furious movies is superior to using git or v1,v2 v3🤮.
New glorious naming convention -
The File tracker 2 File 2 Tracker The Fi...
For Example If you consider Google Workspace is the product and Google Docs as a feature, how do you cover all the features of Google Docs in a single document?
How do PR reviews happen in your company? Are there any guidelines you follow to ensure Swift and meaningful reviews on your contributions? Any input or opinions are welcomed