Although it is not a critical factor when choosing your issue tracker, it still affects your team. This can be pretty annoying if you are skimming through several commits or PRs and want to check all the referred issues. This means that if somebody inserts an issue reference in a commit message or pull request, you will need to manually copy the issue identifier, open the YouTrack page, and paste the identifier into the search field. GitHub does not recognize the issue references, and will not provide a link to your issue tracker. The same is not possible if you are using an external issue tracker such as YouTrack. As I previously said, if you are using GitHub issues, you can navigate to your issues from the commit/PR page. With those commits, you can also perform operations on your issues using commands.īut I feel there is still a missing piece. With this integration, you can refer issues from your commits, and YouTrack will be able to tell you which commits and Pull Requests (PR) are related to your issue. When you start using YouTrack, you will be interested in integrating your code repository with the issue tracker. But if you are developing the project professionally, you will probably want to use a more powerful tool such as YouTrack, enabling, for instance, powerful reporting and workflows. It is configured out of the box, and your commits and comments can have hyperlinks to your issues if you refer them. When assessing the issue tracker to use in a project, if the project is hosted on GitHub, it is really easy to start using the GitHub issue features. Please post your questions as comments below, and the author will address them. This guest blog post is brought to you by Nuno Pinheiro, the author of a Chrome extension for navigating to your issues from a GitHub commit/PR page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |