youngmon/atlassian-qna huggingface dataset:
How to add branches starting with release under 'Branches allowed to deploy' in Repository settings?
Asked by Gangadhar Malana:

I have more than 2 Release branches and will be more in future I want to add all the branches starting with Release to the 'Branches allowed to deploy' in repository settings-\> Test environment, I am looking for any glob pattern, something like this : release/\* , but not this as it is not working.


Answers:
author: Theodora Boudale
body: Hi [@Gangadhar Malana](/t5/user/viewprofilepage/user-id/4658371) and welcome to the community.

The glob pattern **release/\*** should work if you are running builds based on branches and if the deployment step has the deployment keyword with the name of the environment where you set up this rule, e.g. like this:

```
- step:
    name: Deploy to staging
    deployment: Staging
    script:
      - echo "Deploy to staging"
```

* Could you please let us know how you have configured builds in your yml file for release/\* branches?  
  Are they running as part of the default pipeline?  
  Or do you have a definition for

  ```
  branches:
  ? release/*:
  ```

  Or a different setup?

* Does the deployment step have the keyword **deployment** along with the name of the environment where you set up this rule?
* When you say that this is not working, do you mean that commits in other branches trigger the deployment step as well?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
SourceTree commit single file
Asked by sadlerville:

As of SourceTree 1.9, there does not seem to be an easy way to commit a single file. In version 1.8 you could right click on a file and commit an individual file, but the feature is gone in 1.9.

The only way I can see to commit a single file out of a bunch of changes is to unselect all of the checkboxes, tick the checkbox next to the file I want to commit and then commit normally.

What happend to the right-click Commit option? I can Log, Blame and Reset an individual file via right click, but not Commit.

Thanks.


Answers:
author: Seth
body: Try reading through [this blog post](http://blog.sourcetreeapp.com/2014/04/29/sourcetree-for-mac-1-9-out-now/) about the main changes in 1.9, and see if the description there help you make things more efficient. In particular, I wonder if restoring the staging area would remove the need to uncheck files.


author: sadlerville
body: I see from the comments in the blog post that you mentioned, I am not the only one who finds the new workflow confusing. Using the staging area was a good suggestion. Thanks.
Is it possible to modify the "push changes immediately" option?
Asked by Adam Jakab:

The "Push changes immediately to" checkbox gives me the option to push my commit immediately, but it offers me the wrong remote.

Is it possible to configure this option to use a specific remote?

My current branch is origin/master, the option offers me the demo/master branch. (my repo have two remotes: demo and origin, both have master branch)

Thanks in advance!


Answers:
author: KieranA
body: Hi Adam,

This will always work for your 'origin' remote. You could change your origin by going into your repository settings and changing the names of the remotes to switch to the remote you always want to push to. Generally this is the default because that's the remote you usually push to.

Cheers

comments: author: Adam Jakab
body: If I change my origin remote's name to 'default', then I see the "push changes immediately" option as default/master but then immediately changes to demo/master


author: Adam Jakab
body: After several restarts now it's working with the name "default", thank you for the answer!


author: XaeroDegreaz
body: You can fix this issue by going to:

**Preferences \> Git \> Set "Push branches" to "upstream"**

**![](http://snag.gy/oSx21.jpg)**


author: SimonW
body: I'm having the same issue. The remote branch that's shown here is stuck on the wrong remote branch "tony.t/master" when the branch is tracking "origin/master". I've tried set the branch to track different remote branches, and even deleted and recreated the branch but it stays stuck on "tony.t/master".

comments: author: SimonW
body: My \`\~/.gitconfig\` has \`push.default = matching\`, which matches the setting in SourceTree prefs. I can confirm that running \`git push\` on the command line does push to the correct remote branch, as opposed to SourceTree, which doesn't.

Interestingly, the prefs dialog doesn't work for me. When I open it it can't be closed. Even after restarting and closing all the open windows. Maybe the prefs need to be cleared? I tried trashing \`\~/Library/Preferences/com.torusknot.SourceTreeNotMAS.plist\` but didn't help.


author: Seth
body: Try modifying your git configuration file manually. If necessary, you can find it through the SourceTree options dialog.


author: Seth
body: push.default isn't really relevant. It effects which branches get pushed, not which remotes they get pushed to.

Check out [this answer](http://stackoverflow.com/a/4847136) from stack overflow.


author: SimonW
body: ```
Yeah, thats not it (I do know how to use git). Heres the section fir that branch:
```

```
[branch "master"]	remote = origin	merge = refs/heads/master
```


author: Seth
body: Sounds like a SourceTree bug. I'd file a report at [jira.atlassian.com](http://jira.atlassian.com). Post a link to the bug report here so others can vote it up.
fatal: cannot do a partial commit during a merge. Completed with errors, see above
Asked by eric franchomme:

With the new version of SourceTree (1.9.0), I am getting commit errors that I was not seeing before.

The main one is trying to Commit changes brought to a branch from a Merge. the local repo contains other changed files that I do not want to associate with the commit (basically, I only want to commit the files that were changed from the merge, and leave the other files out of the commit). It used to be possible prior to 1.9.0. 1.9.0 broke that option.

any workaround?


Answers:
author: Seth
body: Try stashing/shelving the changes in your local repo prior to the merge.

comments: author: eric franchomme
body: that's inconvenient as it adds more steps to the process, and error prone, as it's easy to forget to stash; and also, once I stash, I can not test the results of the merge: the files that were already in the local repo are for Settings/Testing purposes.


author: Seth
body: It is generally advisable to keep settings files out of the repository (they can be in the working directory, but ignored). If you have them in the repo for documentation purposes, I recommend putting them in with an extra piece in the filename.

For example, if your settings are in 'settings.ini', rename the settings.ini in the repo to settings.default.ini, then make it part of standard deployment steps to copy that file to 'settings.ini', then modify it. If this occurs in a repository working copy, the 'settings.ini' file can be safely ignored.
Hierachical View on SourceTree is gone
Asked by Oleg Cohen:

With the latest SourceTree update I can't seem to find a way to view pending changes and new files. It was very convenient and allowed to stage entire folders.

Thanks, Oleg


Answers:
author: Seth
body: This has been hashed out in detail on this [other question](/questions/289308/how-do-i-get-the-file-tree-back), and repeated in countless others. Instead of continuing to complain to the community (most of us have no influence over SourceTree development), please go to the relevant bug report in that post and vote.
Sourcetree 'Working Copy' view stuck showing one file in diff mode
Asked by John Hile:

After updating SourceTree to 1.9, I did something that causes my 'Working Copy' view to always display only a single file in diff mode. I can find no way to get it back to showing me my list of files. If I select to display 'pending', I see one pending file in diff mode. If I select all, I see one (different) file from among all the files.

I've tried refresh, reinstalling, and cloning a new project from bitbucket -- no change.

I even tried reverting to 1.8.1 -- same behavior with older diff view, then upgrading to 1.9 again. Nothing helps.


Answers:
author: KieranA
body: Hey John,

Looks like you hit a bug which causes your view to be remembered like that. This has been fixed now, but if your preferences are set like that then it'll stick around regardless of what version you install. To fix this, on the left of that pane there's a border which is twice as thick as other borders. This is because it's two borders stuck together (both are splitters that can be adjusted). You can reveal that view again by grabbing the right hand one, which is quite difficult as they're 1px wide, but it is do-able. Grab the right hand splitter line and drag it to the right to reveal the missing view.

Hopefully that makes sense, but if not, feel free to question the problem again.

Cheers

comments: author: John Hile
body: That did the trick. Thanks so much for the answer. Going without for a couple of days made me reallize how much I use and appreciate SourceTree.


author: Brandon Gresham
body: I just ran into this issue with 2.0.3 -- thanks so much for the answer, this worked perfectly.A suggestion for the Atlassian folk is make it so that this middle-windows cannot be collapsed completely -- I can't imagine any use-case where you'd want to completely hide it anyways.


author: crichmond
body: Been suffering through this for months! Putting it into "Tree View" would at least show all files/changes, but they were totally unnavigable. Thanks much!


author: Karl Becker
body: Agreed - this fixed things for me. Having an update that just bumped up the minimum width in a user's preferences would be nice, but glad I found this.


author: ivyyangthl
body: It saved my day!!


author: Oleh Kolinko
body: Thanks a lot, I tried different views and thought it's a bug. It should be more obvious that it was hidden


author: DanielBergstrom
body: I just ran into this now on version 3.1.1 (213). Thanks for the answer! It was really confusing to only see one file.

The answer is a little confusing though saying that it has been fixed. It looks like the problem has been there for over five years now.
Committing to a new branch to hg repository always commits modified files even when they're not selected
Asked by xyz_st:

When creating branches, we tend to do an empty commit just to create the branch. However if you have modified files in the working copy when doing so, SourceTree seems to commit those files too even though they're unselected in the commit window.


Answers:
author: xyz_st
body: This is in Mercurial, not git, so you can't just 'push'. You have to commit to a new branch.

And regardless, if the files are un-checked in the commit window, SourceTree should not commit them, that is a bug.


author: Seth
body: Why do you do that? Try just right-clicking the new branch and pushing it to origin. It won't be displayed as a branch in the graph, but that doesn't mean it isn't one.


Tags: windows
Close branch disabled for branches prefixed with 'feature/' in mercurial repository
Asked by xyz_st:

We don't use hg flow but do name our branches in a similar fashoin. E.g. I've just created a branch called

feature/test

But I can't close it. If I right click on the branch, close branch is disabled. For branches not prefixed with feature/ 'close branch' is enabled as expected.

I've just updated to 1.9.0 and think this problem has just appeared but I can't be sure.


Answers:
author: xyz_st
body: I've just upgraded to 1.9.1. It looks like I can close a 'feature/' branch provided that it isn't the active branch which seems a little odd but is a workaround for now.
How do i search a commit using filename ?
Asked by amanpreet_singh:

There are no way i can search all commits for a particular filename from search view. I need to go to file and then do log selected.

In search options i see commit, changes, commit message etc but not filename. This should be improved.

Also i feel there is no unified search which will search anything from filename,commit message to user etc.


Answers:
author: Seth
body: I think you are correct, I've never found a way to do this either. You could search for and/or submit a feature request at [jira.atlassian.com](http://jira.atlassian.com). If you do, post a link here so others can vote for it.


Tags: file

search
stage several files on new SourceTree Mac version
Asked by Renato:

I just updated my MAC SourceTree to the Version 1.9.0. This version made some design modifications and one of them was on how to state files to a commit.

Before, we could stage files by dragging them from the "unstaged" to the "staged" section. In the new version, the "stagged" section was removed and you stages the files by checking the checkbox on the each filename.

The problem with that approach is that if I want to stage several files at once (let's say, during an initial commit), I have to check each checkbox one by one....

Is that really the only way? Or is there a easier way to stage multiples files?


Answers:
author: Seth
body: You can Cmd+click to highlight multiple files (maybe shift+click as well), then hit the space bar once to check (stage or unstage, depending on current status) all highlighted files.

comments: author: Seth
body: <http://blog.sourcetreeapp.com/2014/04/29/sourcetree-for-mac-1-9-out-now/>


author: Renato
body: Thanks for the blog link. It (together with the comments) summarizes everything.
Difficulties with version 1.9.0 (1.9.0)
Asked by Tsahi Deri:

I updated my SourceTree client to version 1.9.0 (1.9.0) on MAC.

I have some difficulties In the flie status view:

1. When I check an unstaged file it automatically stage it. Can it be cancel ?

2. Each file is represented by its full path. Can I change it to represent by file name only ?

Regards,

Tsahi


Answers:
author: Seth
body: 1. Uncheck it.

2. No, but they are going to modify how that is displayed in 1.9.1

For other 1.9.0 issues, check [this question](/questions/289308/how-do-i-get-the-file-tree-back)to see if it has already been addressed.
Can we share SourceTree license in the company?
Asked by Taku YASUI:

We're now trying to use SourceTree in our company. It passed 30days and then, it requires us to register my email address to [my.atlassian.com](http://my.atlassian.com). But do we need to register all of us to use it? we have many employees and it seems difficut for us.

So, can I share single license key file registered by me?


Answers:
author: Cathy Sanders
body: We also had this same question and we followed the suggestion provided by Atlassian to register via a corporate e-mail address:

[](/questions/166460/what-is-the-best-way-to-register-for-sourcetree-licenses-as-an-enterprise?page=1#166825)<https://answers.atlassian.com/questions/166460/what-is-the-best-way-to-register-for-sourcetree-licenses-as-an-enterprise?page=1#166825>

comments: author: Seth
body: +1 for linking an old answer.


author: Timothy
body: Oh common.. It's free right ;)


Tags: licence
Password Keychain
Asked by micknudsen:

Hi,

I have just reinstalled Mac OS X Mavericks and at the same time upgraded to SourceTree v.1.9.0. One of these two things seems to have caused the following problem: Whenever I want to push changes to a GitHub repository, I am asked for my password.

I have tried suggestions such as including my username in the https address, but it doesn't work. Where does SourceTree store passwords? I have looked in my (Apple) Keychain, but there are no signs of neither SourceTree nor GitHub.

Thanks!

/Michael Knudsen


Answers:
author: micknudsen
body: Turns out that SourceTree also supports SSH. Switched to that from HTTPS, and now everything works like a charm.

comments: author: Seth
body: Glad to hear it.


author: micknudsen
body: Just realized that SourceTree also supports SSH. That solved my problem. Huzzah!!!


author: Seth
body: There should be a list of saved credentials in the authentication tab of the options dialog.

comments: author: micknudsen
body: Where do you find the options dialog? I have went through all parts of Preferences, but I haven't found anything about authenticaiton. The closest I get is an option to set my username. Here I have tried both my GitHub username and my email address, but neither works. Same problem on two different Macs.


author: Seth
body: I use Windows, where it is simply Tools \> Options... \> Authentication.

I don't know where it might be on a Mac.


author: micknudsen
body: Hmmm ... this is really strange. I can't find anything about authentication. Didn't expect the Mac and Windows versions to be different.


author: KieranA
body: Hi Michael,

It's on the 'Network' tab in the SourceTree preferences.

Cheers


author: micknudsen
body: I have looked at that one, but it only has two columns: "Host name" and "Username". There seems to be no way to also store a password.


author: micknudsen
body: I am in the process of reinstalling Mac OS X on all my machines. Just tried on a machine that I haven't touched yet. Things work perfectly, also in SourceTree 1.9.0.

The problem thus appears to be related to my fresh OS installations. Maybe my machines must somehow be authorized with GitHub? I have tried uploading SSH keys but to no avail (which I would expect, since I am using HTTPS).


author: Seth
body: Try initiating an SSH connection to GitHub in a terminal. If it asks you whether you want to accept the server's key, say 'yes', then try authenticating with SourceTree again.


author: micknudsen
body: Still doesn't work. Very strange. This is probably not the right place to ask, but are there any good alternatives to SourceTree on Mac?


Tags: github

keychain

password
I am having trouble while pulling
Asked by Subrata Sarkar:

Hi,

I am using SourceTree on Windows 8.1. Last tile when I tried to pull a repo it broke after downloading around 200 MB of data. Then I copied the source to hard drive and pointed the folder as Working Copy.

I work in two different PCs. The other PC has Win 7 untimate where pulling and pushing work fine. Last night I pushed some changes from Win 7 PC and now trying to pull the changes from my Win 8.1 PC. When pulling I can only see the wheel spinning for indefinite time. I clicked on OK and got the message "Downloading changesets. Please wait...", but nothing seems to be happening (or may be something is happening but I don't know !)

Is it trying to pull the entire repo again?? If yes, why? I already have a working copy pointed.

Please help! I am stuck badly and need this to be resolved asap as I am running out of time :(

The repo is a Mercurial.

Regards,  
Subrata Sarkar

![](../../upfiles/Untitled_63.png)


Answers:
author: Seth
body: Both Git and Mercurial are fundamentally different from centralized systems (Git, SVN) in that they operate by cloning an entire repository (including the full history of the branches you've requested, but not necessarily all remote branches).

If your repository is large and/or your internet connection is slow, it may take a long time to clone everything.

But you're in luck! Since you ALREADY have the repository on your Windows 7 machine, the fastest solution is going to be to copy that repository to your Windows 8 (just using a direct network connection or removable storage), then add that repository to SourceTree on Windows 8.1. Make sure to include the hidden .git folder.
Please revert the pending/staged changes view
Asked by Lukas Stabe:

I appreciate You trying to improve your product, but I honestly think the new interface for staging and viewing current uncommitted changes is no good.

The old way of dragging and dropping files between the staging area and the changes on the working tree worked great. It worked especially great for staging a selection of files at the same time (command-clicking multiple files, dragging them into the staging area) which is a bit more involved now (command-click multiple files, right-click, select "Add to index").

The new view also takes up significantly more space than the old one (I'd estimate each file takes about 1.5 times the height it did in the old version =\> it fits 33% less files).

I also don't like how the staged changes scroll away when i scroll down into unstaged ones.

On the right side in the diff view, staging single lines now requres a right-click. I do, however, like the new, cleaner look more than the old one.

tl;dr: I really don't like the new way to manage uncommitted changes/staging changes, please make it more like the old one :/

For me this means I'll stick with 1.8.1 for now.


Answers:
author: Adrian von Gegerfelt
body: A JIRA ticket for the Staging view:

[](https://jira.atlassian.com/browse/SRCTREE-2267?jql=labels%20%3D%201.9-UX-feedback)[https://jira.atlassian.com/browse/SRCTREE-2267?jql=labels%20%3D%201.9-UX-feedback](https://jira.atlassian.com/browse/SRCTREE-2267?jql=labels%2520%253D%25201.9-UX-feedback)

I can't log in to vote, for some reason...


author: Seth
body: Bug reports for this issue and many others have been linked in this question:

[](/questions/289308/how-do-i-get-the-file-tree-back)<https://answers.atlassian.com/questions/289308/how-do-i-get-the-file-tree-back>


author: Adrian von Gegerfelt
body: One more thing - the new view is also incredibly slow! I have over 50 modified files, and I'm still waiting for them to be ticked 'staged' \>:(


author: Adrian von Gegerfelt
body: Also, you can not select multiple files and then "Stage" or "Discard" - the action only applies to one item, even if multiple selected. Was this version even tested?!
What happened to the Finder List view on the Mac version of SourceTree?
Asked by Curt Lewis:

I just upgraded to the latest version and the GUI has totally changed. My repository file list has no folders or tick arrows, it's just a sorted list with no indenting.

Why was this feature removed? The new look is far less useful.


Answers:
author: Seth
body: <https://answers.atlassian.com/questions/289308/how-do-i-get-the-file-tree-back>
SourceTree Filename instead of full path in staging area
Asked by David Lee:

I just upgraded to SourceTree 1.9.0 and I'm trying to figure out how to display the filename in the staged/unstaged files window.

ie. instead of displaying "full/path/to.../filename.txt", I'd like to see just "filename.txt"

How do I change this setting?


Answers:
author: David Lee
body: This is much improved in version 1.9.3. Thank you very much SourceTree team for listening to the feedback and getting around to fixing it. I appreciate it


author: Andrew Shouldice
body: You can't. There's an issue here ([](https://jira.atlassian.com/browse/SRCTREE-2232)<https://jira.atlassian.com/browse/SRCTREE-2232>) where you can voice your concerns.
Error encountered - 'git log' failed with code 128:'fatal: bad revision 'paginationBranch'
Asked by Joel Brown:

I merged the pagination branch back into the master branch, deleted that pagination branch and am now trying to commit changes to the master branch for minor fixes.

I have tried the fetch - prune branch suggestion from a different question without any success.

I am working on a mac, 10.8 with the latest version of sourcetree and github.


Answers:
author: eiger3970
body: I tried checking out master, but there's nothing there?201507131139 SourceTree 2.0.5.2.png  
[](https://community.atlassian.com/t5/Sourcetree-questions/Error-encountered-git-log-failed-with-code-128-fatal-bad/qaq-p/243056?attachment-id=4017){#link_116b80e7a1344a}  
[](/tnckb94959/attachments/tnckb94959/sourcetree-questions/7120/1/201507131139%20SourceTree%202.0.5.2.png){#display_116b80e7a1344a_0}


author: Seth
body: Try checking out master again.