-
Suggestion
-
Resolution: Won't Fix
Recently we've noticed several old open PRs get updated without any human intervention.
This is not the best behavior given our development workflow, which is based around pull requesting from anonymous heads in a mercurial repository and does not use feature branches.
Worse, it appears that pull requests do not actually auto-update at all, instead all pending PRs get auto-updated when another pull request is merged.
For example, last night the following pull requests was merged:
https://bitbucket.org/enzo/enzo-dev/pull-request/206/adding-rotating-sphere-test-problem/activity
This caused the following pull requests to be automatically updated:
https://bitbucket.org/enzo/enzo-dev/pull-request/173/fixes-header-include-order-and-missing/activity
https://bitbucket.org/enzo/enzo-dev/pull-request/199/keep-initially-uniform-metallicity-fields/diff
https://bitbucket.org/enzo/enzo-dev/pull-request/202/adding-the-agora-isolated-disk-problem-and/diff
In all three cases this was not the desired behavior.
I don't think it's a good idea to let pull requests be updated without some sort of manual confirmation from the PR issuer. I would appreciate a way to revert to the old behavior.
- is cloned from
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-22135] Ability to disable pull requests auto-updating
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: migrated | New: migrated timeout-suggestion-bulk-close |
| Link |
New:
This issue is cloned from |
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!