store issues as a private issues branch #100
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses issue #9
In the existing Git repository, the default behaviour has been updated. Previously, the default behaviour was to store the issues in a new issues repository. However, the new default behaviour is to store the issues as a private issues branch within the existing git repository. The -r option can be used to store the issues in a new issues repository.
In cases where the existing Git repository is empty without any commits, it is not possible to create a private issues branch. To resolve this, a commit will be made with the addition of the .git-issues-init.txt file. This commit will appear in the project's Git log, indicating that git-issue is now initialized in the project.