say we have Repo1, and Repo2
Repo2 is a subtree in Repo1, both the respostories have thier issues.. which gets resolved when we commit code.. using the command during commits ex "Resolved issue #111"
Now say in repo2 we have a issue with #111 and i commit the code in repo2 , which would automatically resolve #111 in repo2,
Now if i go to repo1 and i do a pull on the subtree (Repo2) in Repo1, i would get the changes done in Repo2 into Repo1, and when i do a Push...the changes that i got from Pull, since the Repo2 changes contain the command
"Resolved issue #111"
Its automatically resolving #111 issue in Repo1
It should not be doing that.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs