issue-tracking | 易学教程

Jira issue number in git commit message

阅读更多关于 Jira issue number in git commit message

问题 At our company we are moving from svn to git. For issue tracking we use JIRA from Atlassian. Now we want to enforce that every commit message contains an issue number (just like we did with svn). We have found the commit-msg hook which we use to reject a commit if it does not contain an issue number. JIRA uses Fisheye to scan the git repo. If a commit message contains an issue number then the changes are shown under that issue. The problem is that a hook is not copied when a git repository is

Setup JetBrains YouTrack to connect to SVN

阅读更多关于 Setup JetBrains YouTrack to connect to SVN

问题 I realize that TeamCity must be a bridge between YouTrack and SVN, but I need none of the Teamcity functionality. I just want to issue Youtrack commands via commit comments like here: http://confluence.jetbrains.net/display/YTD3/Executing+Commands+from+Comment+to+VCS+Commit i.e. a commit message test #ld-1 fixed Would mark the issue ld-1 as fixed. I'm sure I set up youtrack, teamcity and svn correctly, however what I came to realize is that I need to make a build step in TeamCity that will be

Why Mylyn is not getting issues from GitHub?

阅读更多关于 Why Mylyn is not getting issues from GitHub?

问题 I recently started to use GitHub Mylyn connector for Eclipse and I have it working, I create new tasks and I can see them in Eclipse and GitHub. The problem is when me or someone else create an Issue on GitHub I can't see it on Eclipse. I have done this and configured Mylyn on that way as you can see in the image: But as you can see under "Bugs and Enhancements" I have nothing and here I actually have one issues, so, why don't they appear? Is something to do with the fields Assigned to and

No issue tracker button in bitbucket?

阅读更多关于 No issue tracker button in bitbucket?

问题 I'm trying to set up issue tracking on a bitbucket private repository, but there isn't a button to manage/add issues. In this tutorial from atlassian, it clearly shows the issues and wiki buttons, however this must have been before they created pipelines because that button isn't there either. Here's what my sidebar looks like: The last blog post I found on their blog relating to issue tracking was about a UI update for managing issues. In the blog post announcing the release of pipelines

What headaches should I expect from using Trac?

阅读更多关于 What headaches should I expect from using Trac?

问题 No tool is perfect, and I'm about to start several long-term projects using Trac, and wanted a heads up of the kinds of problems I may or may not experience with it. In other words, Trac meets my needs in the short term, and I've already made the decision to use it , but I want to know what to expect down the road. I am not looking for: "Use product X instead of Trac because..." answers. "Trac is great because..." answers. A comparison to any other specific system. "Trac doesn't support

How to restore accidentally deleted Gitlab issue?

阅读更多关于 How to restore accidentally deleted Gitlab issue?

问题 It seems I have accidentally deleted a Gitlab issue. Is there any way to restore it? 来源： https://stackoverflow.com/questions/53629896/how-to-restore-accidentally-deleted-gitlab-issue

No issue tracker button in bitbucket?

阅读更多关于 No issue tracker button in bitbucket?

I'm trying to set up issue tracking on a bitbucket private repository, but there isn't a button to manage/add issues. In this tutorial from atlassian, it clearly shows the issues and wiki buttons, however this must have been before they created pipelines because that button isn't there either. Here's what my sidebar looks like: The last blog post I found on their blog relating to issue tracking was about a UI update for managing issues. In the blog post announcing the release of pipelines here shows a screenshot that has the same sidebar layout as I have, no issue tracking or wiki button, just

Closing a GitHub Issue while on a different branch

阅读更多关于 Closing a GitHub Issue while on a different branch

I am not working on the Master branch. I am working on a different one newFeature , which is also published on github. I know how to to close issues when working on the Master branch: Closes #XXX . However this only works when I am working on the Master branch, if I switch over to the other branch or a different one and do a commit with Closes #XXX it does not close the issue. My question is: Is it possible to do this and how do you do it? i'm pretty sure github issues are agnostic of branches. are you talking about a local branch or a tracking branch? if your not specifically tracking the

Is there a standard file format for exporting issues from an issue tracker?

阅读更多关于 Is there a standard file format for exporting issues from an issue tracker?

问题 Background: I've written a backup tool for the Mercurial/Git hoster Bitbucket, which asks for a username, gets a list of the user's repositories via the Bitbucket API, and clones each of them to the local machine. Each Bitbucket repository has an issue tracker, and now I've got a new feature request: backup the issues as well. I can actually get the issues in JSON format from the Bitbucket API. Here is an example: https://api.bitbucket.org/1.0/repositories/christianspecht/bitbucket-backup

remove deleted commit that references an issue

阅读更多关于 remove deleted commit that references an issue

问题 I amended a commit a few times and did push --force each time (stupid mistake; I didn't realize until getting ready to send a PR that my editor had generated tons of noise by fixing tabs and trailing whitespace). The commits that I thought were no longer existent are still reachable on GitHub, and the issue reference causes a list of links to these non-existent commits to appear: How do I get rid of these commits on the GitHub remote so that these extra links will go away? 回答1: In general,