Issue tracker for gitea repositories

Go to file

Maxence G. de Montauzan f398c17c60 Update packages & vscode engine Remove (old) tests Update some methods to new version		2022-08-17 15:27:58 +02:00
.github	Create Funding.yml	2019-08-04 19:10:53 +02:00
.vscode	A bit of cleanup	2019-07-04 15:45:53 +03:00
media	ADDED: Image to README.md	2019-04-12 08:42:45 +02:00
resources	Version: 0.0.8	2019-07-29 09:43:37 +02:00
src	Update packages & vscode engine	2022-08-17 15:27:58 +02:00
_config.yml	Set theme jekyll-theme-slate	2019-08-04 12:18:10 +02:00
.gitignore	feat: add test environment with docker-compose	2021-03-12 21:12:40 +01:00
.vscodeignore	A bit of cleanup	2019-07-04 15:45:53 +03:00
CHANGELOG.md	chore: update changelog	2020-12-31 13:54:45 +01:00
CONTRIBUTING.md	Updated README.md	2019-10-11 18:56:00 +00:00
docker-compose.yml	feat: add test environment with docker-compose	2021-03-12 21:12:40 +01:00
LICENSE	Version 0.0.3 - View Changelog for more information	2019-04-10 13:45:47 +02:00
package-lock.json	Update packages & vscode engine	2022-08-17 15:27:58 +02:00
package.json	Update packages & vscode engine	2022-08-17 15:27:58 +02:00
README.md	Updated README.md with new config approach	2021-09-28 16:53:16 +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

README.md

Gitea-VSCode

Issuetracker for Gitea

Overview

Gitea-VSCode is an Visual Studio Code extension that allows you to manage (currently only view) your issues.

Support

Getting Started

Go to your settings, and find the Gitea section, and fill out the details.

Please make sure not to make your authtoken public, as it can be used to act on your behalf. Keep instance key "gitea.token" in user settings other section keys keep in .vscode/settings.json.
Otherwise do not push the .vscode folder to your repository and doublecheck this part. It contains your gitea server instance key.

Config example

go to https://%YOUR_GITEA_SERVER/user/settings/applications and Generate Token
fill ,"gitea.token": "%YOUR_KEY%" in VS code user settings in following locations:
- Win %APPDATA%\Code\User\settings.json
- Mac $HOME/Library/Application Support/Code/User/settings.json
- Linux $HOME/.config/Code/User/settings.json
fill in .vscode/settings.json

    , "gitea.instanceURL": "%YOUR_GITEA_SERVER%"
    , "gitea.owner": "%OWNER%"
    , "gitea.repo": "%REPO_NAME%"

The following details are needed

Authtoken
Port (either 80 or 443) in case that you use docker please enter the exposed port
BaseURL (default to "") in case you have your instance reachable on a suburl.
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).

Issue colors

In order to get nice looking issue icons in multiple colors (of your choice) you just need to assign a label to your issue. The color is being fetched automatically. In most cases you need to restart visual studio code to apply the icons in the issues tab if you've changed them though.

Contributing

Please refer to each project's style and contribution guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.

Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!

Roadmap

Implement a Close Issue Button
Create Issues via Webview
Comment Issues
Support multiple git servers