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.
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.