git-bug is a bug tracker that: is fully embedded in git: you only need your git repository to have a bug tracker; is distributed: use your normal git remote to collaborate, push and pull your bugs! works offline: in a plane or under the sea? Keep reading and writing bugs! prevents vendor lock-in: your usual service is down or went bad? You ...

BugTracker.NET is a web-based bug tracking system that has git integration. The web pages for the git integration look pretty much like the ones for the subversion integration, documented here . You can read more about the philosophy that guided BugTracker.NET/Git integration in this Stackoverflow question: How does bug tracker/version control ...

4 天之前 · react nodejs tracker typescript frontend backend reactjs bug-tracker bug postgresql expressjs ts full-stack issue pern pern-stack Updated Oct 28, 2023 TypeScript

You can create issues in your repository to plan, discuss, and track work. Issues are quick to create, flexible, and can be used in many ways. Issues can track bug reports, new features and ideas, and anything else you need to write down or discuss with your team.

Public Bug Tracker for Dota2. Please submit gameplay bugs for the Dota team to look at here. We'd like to use the "thumbs up" reaction as an upvote to track priority from the community, so to "+1" an issue please add a thumbs up reaction to it.

Below we are creating an issue template for reporting a bug in Project Octocat. Now that we created the bug report issue template, you are able to select it when creating a new issue in Project Octocat. Opening issues and using task lists to track work. You can organize and track your work by creating issues. For more information, see Creating ...

Give your developers flexible features for project management that adapts to any team, project, and workflow—all alongside your code.

git-bug is a standalone distributed bug-tracker that is embedded in git. In short, if you have a git repository you can use it to store bugs alongside your code (without mixing them though!), push and pull them to/from a normal git remote to collaborate.

Add a description that explains the purpose of the issue, including any details that might help resolve the issue. For example, if this is a bug report, describe the steps to reproduce the bug, the expected result, and the actual result. You can use markdown to add formatting, links, emojis, and more. For more information, see Writing on GitHub.

You should fix the bug: $ echo my great fix >> foo And then tell Gitbug what you did: $ git commit -a -m 'foo: fixed bug, FIX[.*first]' or $ git commit -a -m 'foo: fixed bug' $ gitbug close .*first That fix wasn't a fix at all, let us reopen the bug: $ gitbug reopen .*first Make a second bug: $ gitbug add Bug number two Oh, it is a duplicate of ...