Github user MJJoyce commented on the pull request:
https://github.com/apache/climate/pull/221#issuecomment-130410320
Truthfully @huikyole I don't see how managing this in a different branch is
too complicated. The changes aren't dependent upon each other in any way so the
branches don't even need to be merged together while you're doing your work
right?
```
# Notice the thing to fix, make new JIRA for it
git checkout master
git checkout -b CLIMATE-<new ticket id>
# make the quick changes and commit
git push github CLIMATE-<new ticket id>
# make PR
```
And you're back to working on your old issue in just a few minutes. Worst
case is there's some minor merge conflict here that takes all of 5 seconds to
fix when you go to merge the PR. Concerns are easily separated then and we're
not burying changes in unrelated tickets. There's also no reason to just remove
the test and not the relevant metric, and that's big enough of a change to be
in its own ticket I would think.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
