Issue tracker for gitea repositories
Go to file
2019-04-11 14:19:42 +02:00
.vscode Inital commit 2019-04-09 14:37:58 +02:00
media Inital commit 2019-04-09 14:37:58 +02:00
resources Version 0.0.3 - View Changelog for more information 2019-04-10 13:45:47 +02:00
src Fixes #1 #2 2019-04-11 14:19:42 +02:00
versions Fixes #1 #2 2019-04-11 14:19:42 +02:00
.gitignore CHANGED: README.md; ADDED: Binaries 2019-04-10 09:06:52 +02:00
.vscodeignore Inital commit 2019-04-09 14:37:58 +02:00
CHANGELOG.md Fixes #1 #2 2019-04-11 14:19:42 +02:00
LICENSE Version 0.0.3 - View Changelog for more information 2019-04-10 13:45:47 +02:00
package-lock.json Fixes #1 #2 2019-04-11 14:19:42 +02:00
package.json Fixes #1 #2 2019-04-11 14:19:42 +02:00
README.md CHANGED: README.md; ADDED: Binaries 2019-04-10 09:06:52 +02:00
tsconfig.json Inital commit 2019-04-09 14:37:58 +02:00
tslint.json Inital commit 2019-04-09 14:37:58 +02:00
vsc-extension-quickstart.md Inital commit 2019-04-09 14:37:58 +02:00

Gitea-VSCode

Issuetracker for Gitea

Getting Started

To setup a gitea issue tracked project you need to first select the issues tab at the activitiy bar. After that open the command palette in order to enter your crendentials:

  • Authtoken
  • Domain in format: "example.com"
  • Repository Owner (may be an organisation): "TestOrganisation"
  • Repository Name "ExampleRepository"

When you've finished you can press the refresh button in the open issues section and you'll see the issues of the first 10 pages (only open issues).

Future

  • Implement a Close Issue Button
  • Create Issues via Webview
  • Comment Issues