Menu
Is possible to store the project issues in its git repository?
I know that git doesn't support this feature and the issues are stored in the provider site (eg. Bitbucket, Github).
I would like to develop a project as a free private repository on Bitbucket, and when it is finished to make it open source moving it to Github. The problem is that the issues reported in the Bitbucket repo will not be available in the Github repo, because they are stored in the Bitbucket databases.
Which is the best solution?
700
To link related issues in the same repository, you can type # followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
Repositories. A Git repository is simply a database containing all the information needed to retain and manage the revisions and history of a project. In Git, as with most version control systems, a repository retains a complete copy of the entire project throughout its lifetime.
You shouldn't store credentials like usernames, passwords, API keys and API secrets. If someone else steals your credentials, they can do nasty things with it.
For example, if you use the New Project Wizard to create a New PHP Project from Git and the repository is remote, Eclipse/EGit will happily create a project folder in the Eclipse workspace and put the repository (. git) in the project folder.
Issues are kind of orthogonal to code (i.e. they transcend version snapshots), so it's useful to have a separate system for them. As such, git has no built-in system for issue tracking.
Since BitBucket and GitHub both have APIs for issues, there are easy ways to migrate the issues across. Searching for "migrate bitbucket issues to github" produces at least one script to do exactly that.
83
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
