3 ms·
In my opinion, the cost of creating branches, checking out, creating PRs, and ensuring they are part of the appropriate release can't be ignored. I have seen it
by shubhamjain 7y ago
In my opinion, the cost of creating branches, checking out, creating PRs, and ensuring they are part of the appropriate release can't be ignored. I have seen it happen. The backlog is high but no one wants to pick an issue (say, a styling bug) even if they have time, just because the number of steps involved in getting it to production is too damn high. If you only had to worry about your change, there would be far fewer of those bugs.
- HelloNurse 7y agoIf you only had to worry about your change, your work would be easy and you would be paid much less.
- anticristi 7y agoIs this high cost inherent to PRs or are there other processes around them (e.g., create a ticket with a long description) that raises the cost? I feel a certain costs for PRs is good: You better leave that styling bug unfixed, rather than breaking the whole website in production.
- codingdave 7y agoI don't feel that pain - it takes seconds to make a new branch, seconds to push it up, maybe 30 seconds to turn into a pr, add a description and some comments, and after it is review, merge and let CI/CD take over. Now, without CI/CD, I could see it as far more painful. But I'm not sure that has anything to do with PRs. Even taking PRs out of the mix, you're still having to get it to production.
- moltar 7y agoAll of that can be automated via CLI. Here are a few tools: - hub https://github.com/github/hub https://github.com/github/hub - lab https://github.com/zaquestion/lab https://github.com/zaquestion/lab - git-extras https://github.com/tj/git-extras https://github.com/tj/git-extras