Git

Issues

Track bugs, tasks and ideas per repository.

Open an issue

In the Git portal, open a repository's Issues → New issue. Anyone in the organization with git:read (every role) can open issues and comment.

  • Title: up to 256 characters.
  • Description: Markdown, up to 64 KB.
  • Labels: comma-separated, up to 10, each up to 32 characters.

Issues and pull requests share one number sequence per repository: if #4 is an issue, the next pull request is #5.

Comment, edit, close

  • Comments are Markdown, up to 64 KB, from anyone with git:read.
  • Editing the title, description and labels, and closing or reopening, is open to the issue's author and to members with git:write.

Issues, in the repository's sidebar, lists open or closed issues, newest first, with their labels and comment counts; the sidebar item shows how many are open.

Assignees, mentions and email

Issues and pull requests take up to 10 assignees from the organization. @handle in a description or comment (the part of a member's email before the @) links to that member.

Members get an email when someone else assigns them, or mentions them for the first time in a description or in a comment, with a link to the issue or pull request. Mentions inside code blocks don't count, and nobody is emailed about their own changes.

Turn these emails off for an organization, or mute single repositories, in the Git portal under Notifications (https://git.cactive.com.au/settings/notifications); a repository's Mute button does the same from its page.