![]() ![]() ![]() Note: This feature won’t appear in the App Store version as Apple does not allow helper installs. Simply install the Command Line Tools from the ‘SourceTree’ menu, and you’ll be on your way. Launch SourceTree to the closest repository containing your working directory – straight from the command line with the ‘stree’ command. Supply a full regex match & replace string to replace any text with HTML that can link to any of your external projects. Gain historical context and a further understanding of the why’s behind your team’s commits.įor those power users who want to dive a little deeper (I know you’re out there!), this feature is actually a specific use-case for another feature: regular expression replacements in commit messages. If you are interested in a particular commit and want to explore the JIRA issue, just click on the issue key, and you will jump right into your issue tracker. In SourceTree, the log view allows you to browse through the history of a project, and you can easily identify all the commits that have JIRA issues associated with it. When closing off a recent JIRA issue, you include the JIRA issue key in the commit message (e.g. SourceTree will automatically link JIRA issues keys or Crucible code review ids that are referenced in your commit messages. Users can now manage their repositories with SourceTree and link back to JIRA issues and Crucible code reviews. Many of our SourceTree users are using Atlassian tools such as JIRA and Crucible as part of their development process. Run them with just a click of a button (or shortcut key)! Integrate with JIRA and Crucible Just add your script to the custom action preferences, and these actions automatically appear in the correct menus depending on what parameters you reference. Practically any action outside of SourceTree can be configured into a custom action. External scripts: hook into the context log and run external scripts for deployments, builds and testing. ![]() Easy peazy! Note: You can configure this handy shortcut with any text editor. We’ve even bound the custom action to a keyboard shortcut. Now, we don’t have to check out our source and then open the directory we can open it straight from SourceTree. Internally, a few of us use Textmate, so we’ve created custom actions (and a handy shortcut) to jump directly to Textmate. Text editors: many SourceTree users jump back and forth between the SourceTree app and their text editor.In the words of SourceTree users: “This process is so important – just support it already!” Plead no more my friends – the new custom actions feature allows you to run your own scripts or processes right in SourceTree’s menus as if they were built in. Sometimes, a script is so valuable to your development workflow that you just wish the action would be built-in to the product. More details of this feature are available in the Help. Let us know what you think of the new submodule and subrepository support. Developers need specific versions of a library in that have not been released, or prefer working with the source code.Software projects often times have dependencies on third party libraries.Git submodules are simply a reference to another repository at a particular snapshot in time. What’s New in SourceTree 1.3? Submodule & Subrepository Supportįeel free to use Git submodules or Hg subrepositories with your projects – SourceTree now supports both. Plus, SourceTree is now FREE for all users, forever. We’re peeling back the covers on SourceTree 1.3 and we are announcing a fresh new logo, a redesigned website, and a new set of useful features to support your DVCS workflow. SourceTree 1.3 – Ready for Takeoff By Steve on January 31, 2012 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |