From: P R. <pa...@ma...> - 2014-10-19 16:20:31
|
Apologies if anyone got some github notifications this morning - atrol got a few and gave me a poke so I was able to stop script that was generating them. I've got a simple script that I basically use to automate some merging and testing In essence, I was feeding in a batch of updates to update sql format for the db layer for 2.x to keep it up to date, and trying to do a local build to test. Usually this works quite well, and I've used it multiple times before - it basically takes a change, pushes it into a new local branch, runs a build and then tidies up at end if all builds pass, or leaves files if they don't. This was working its way through ~500 changes: Anyway, What happened here is I had a pending change for master in my local master (https://github.com/mantisbt/mantisbt/pull/378 ) for pushing. So instead of pushing locally, it pushed for a new remote PR (hence as atrol spotted, the reason for 2 commits in the branch) On the bright side, if atrol hadn't have spotted it, there were a considerable number more branches that would have been generated. Paul |