Tagging some commitment as
I "tested" or "disapproved" Based on the success of some regression tests (clearly labeled)
However, I would like an warning while trying out the old attempts at checkout, which have been rejected or have not been tested at all.
It would be nice if anyone pulls from the repository, tags (and similar warnings will be found even after examining the rejected versions).
If you specify that they want ( git push -tags ) , Tags of GET will go to the repository. There will be no automated alerts, but maybe they can be made.
But you are asking about the best practices:
I do not think cherry is the best practice of team members, in general, people will declare that their treasures Which branches have "known good" code, they will also make changes in the cutouts that are "bad knowledgeable". If you never see more than a single commitment, then you have to return.
I would say that using more than one communication channel is another best practice:
- Announcements
- Cross-Reference Commit and Your Issue Tracker Issues in
Comments
Post a Comment