nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What purpose of refs/pull-requests/123/merge-clean and other?

Alexey_Efimov

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?

Accepted answers

Alexey_Efimov

I'm just researching this by myself. The answer is:

refs/notes/pull-requests/199/merge

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.

refs/pull-request/199/from
refs/pull-request/199/to

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.

All comments

Alexey_Efimov

I'm just researching this by myself. The answer is:

refs/notes/pull-requests/199/merge

refs/pull-request/199/from
refs/pull-request/199/to

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

seb

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.

Alexey_Efimov

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 )

http://blogs.jetbrains.com/teamcity/2013/02/06/automatically-building-pull-requests-from-github-with-teamcity/

And a lot of stackoverflows like this one:

http://stackoverflow.com/questions/12634440/teamcity-building-git-github-pull-requests

Did you know the best solution to automatically track Pull Requests with success Automerge result?

Semyazz

I completely agree with Alexey and I was looking for identical feature to connect Stash's pull requests to TeamCity

Alexey_Efimov

BTW, https://github.com/mendhak/teamcity-stash

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server