Stash creates refs in Git for each Pull Request:
refs/notes/pull-requests/199/merge refs/pull-requests/199/from refs/pull-requests/199/merge refs/pull-requests/199/merge-conflicted refs/pull-requests/199/merge-clean refs/pull-requests/199/to
Is there some documentation about thiese references? How i can use it in Continues Integration server?
I'm just researching this by myself. The answer is:
Contains notes for refs/pull-requests/199/merge. Stash use git notes for this and put into notes list of conflicted files. I'm expect to find here comments, but no luck, comments are not stored in this note. This is used only for conflicts.
Actually point to 'from' and 'to' branches for pull request.
refs/pull-requests/199/merge refs/pull-requests/199/merge-clean refs/pull-requests/199/merge-conflicted
Reference 'merge' is a result of merging pull request. If it have conflicts, then symlink reference 'merge-conflicted' is created and point to the same hash. If pull request can be merged withoout conflicts, then symlink 'merge-clean' is created.
It is extremely important to note that these refs are for internal use only. You should never modify or create these refs yourself as you will invariably cause problems with your Stash instance. The pull request implementation detail is subject to change without warning at any point in time.
The only safe way to interact with the Git repositories hosted by Stash is through the vetted APIs and REST interfaces, which we ensure have backwards compatibility and adhere to our contracts.
Thanks for minus :)
Are you seriously think what someone start to modify thiese references? My question is bout using thiese references for readonly access, as for example, from Continues Integrations server, such as Bamboo or TeamCity. Look into this post to take a little bit knowledge about world outside Atlassian :))
And a lot of stackoverflows like this one:
Did you know the best solution to automatically track Pull Requests with success Automerge result?
Seb, is there any update on how to get at this information in a supported fashion? We're trying to set up a bamboo server to build in response to pull requests, using a fork-based collaboration model where there isn't a branch created on the central repo for the feature being PR'ed (only on the developer's fork) and we can't seem to find any hooks in the docs that we could code against to trigger Bamboo when a PR is created.
I'd like it to be supported in other build systems too, though - we use Teamcity. It's a shame to have to rely on internal implementation details - it's an important feature to be able to build the post-automerge code as opposed to just the source branch code. It's also worth pointing out that as of Stash 2.9.x, _merge-clean_ appears to have been renamed _merge_.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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