ijustdev / gitea-vscode Goto Github PK

Actually when we click on an issue it launch a new tab but it can ends up like this if we're dumb or switching from one issue to another

Could it be possible to have only one tab per issue (when a tab for ex issue 1 is opened redirect it to it instead of opening a new one)

Can't get this extension working with a Gitea running at https://DOMAIN/gitea (behind a nginx reverse proxy).

Tried with SSL and without.

In the dev console I see

ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.
console.ts:137 [Extension Host] Error: getaddrinfo ENOTFOUND https	at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26)

Can't fetch issues; HTTP error

As far as I'm aware, there currently is no way of sorting issues in the extension window. Using the extension in a huge repo with many team members is impossible since there is just this huge list of unsorted issues, most of them not even related to me.

Sorting feature would be great.

Currently it seems like we can only configure a single repo for the extension.

It would be nice if the extension would work on a user level for all repos in the user's Gitea account.

Hello

I've just tried to use this module on vscodium. On sidebar icon is present but in setting panel any gitea configuration are proposed.
Then I can't enable any gitea server.

Thanks a lot

I need to learn your thoughts on this project

Thanks, happy hacking!

Hello there my gitea instance is on https with port 3045 and if i change the settings to my domain 'example.com' and put in port 3045 and the owner and the repo with ssl checkbox checked and a valid token. It is still not working do i something wrong? I always get 'Can't fetch issues; HTTP Error!'

Like git, we can supply a option to allow local "https" protocol but cannot verify SSL certificate.
for example, sslverify = false
And, apply a httpAgent parameter when use axios to get issues.

Display description as HTML

I have configured as follows but returning Error occoured. Error: Request failed with status code 401
Please show us a sample config screen

On Gitea (as well as GitHub, Gitlab, and probably other issue systems using Markdown), list entries starting with a pair of square brackets and either a space or an x in between (i. e. starting with - [ ] or - [x]) are not rendered with the regular list bullet point, but rather with a checkbox.

Example

## Tasks

- [ ] Create repositories and projects as necessary
- [ ] add annotations to declare types to use generated serializers
- [ ] find all applicable types in the project

would be rendered in Gitea as

but is rendered in VSCode as

As a comparison, this is the same from above here on GitHub:

List Nesting

Please keep in mind that since this is done inside of lists, nesting needs to be respected and the indentation should be respected. Here is an example on Github how this could look like:

Checking of Checkboxes

In most issue trackers, checking a checkbox created with this would automatically update the issue by setting an x into the square brackets.

As long as this extension offers only read-only access to the issues, the checkboxes should be rendered as readonly or disabled. This is also used in the preview mode of platforms using this feature.

Once write access to the Gitea instance is established, another feature to be implemented would be to interpret checkbox clicks as edits and updating the issue. However, this is out of scope for this issue and should be implemented afterwards.

Using Gitea 1.15.5
and a fresh installed gitea plugin in VSCode I get this error

Inserting the gitea.instanceURL, gitea.owner, gitea.repo, gitea.token doesn't work when inserted on .vscode/settings.json

Hello

In setting's vscodium miss token option at workspace or folder level.
Otherwise we can set domain, owner, repo and ssl support but not token.
Then it's a bit complicate when we manage follow different gitea instance.

As I use vscodium I can't confirm if it's a bug and different from vscode.

Thank a lot

Parse \n in webview to <br/> in order to display linebreaks as usual.

I just tried to build the extension locally because I wanted to add a feature, and apparently the version of vscode the extension currently depends on causes npm install to fail. If I interpret the error correctly it is because vscode downloads some type definitions on install and either doesn't find the version anymore, or tries to load the latest one which is incompatible - I'm not sure which.
Installing the latest vscode version seems to fix the issue, though I have not checked whether this breaks anything, and also apparently it completely reformats the package.json, which makes it a bit awkward to do a pull request

Due to the percentage of git web interfaces providing access to an API that can be used for fetching issues I would suggest implementing some of them. This would go hand in hand with redesigning the code to be more modular.

What do you think?

Hi,
many thanks for this plugin,
unfortunately, I am not able to get the issues.
Here is my setup:
I have Gitea installed and working in docker env.
My ports are 40000 and 4022
I have a setup for the plugin
Trying to refresh opened issues display "Can't fetch issues; HTTP Error!" in vscode.
Is it a way to display log files? What can be wrong?

many thanks!

This is all the output from VSCode:

[19:35:35.747] Retrieve issues. State: open - page 1
[19:35:35.750] Retrieve issues. State: closed - page 1
[19:35:35.871] AxiosError: Request failed with status code 404
[19:35:35.872] AxiosError: Request failed with status code 404

I've verified my API token is working and that it is touching the API. The base URL is https with no port, connecting to an external domain (running self-hosted). Not sure what other info I can get out of it.

Each piece of code is uniquely addressable via a URI:

`${protocol}${gitea_host}/${repo_slug}/src/commit/${commit_sha}/${tree_path}#L${line_number_a}-${line_number_b}`

It would be nice to have a context menu entry to copy or open this URL in a browser.

I followed the instructions but I get errors:

Config 1:

"gitea.baseURL": "",
"gitea.instanceURL": "http://localhost:5000",

Error 1:

Gitea-VSCode failed to load a configuration value that is needed: baseURL

Config 2:

"gitea.baseURL": "/",
"gitea.instanceURL": "http://localhost:5000",

Error 2:

Error occoured. Error: Request failed with status code 404

vscode 1.54.1
extension 2.0.0

Hey @IJustDev, thanks for the latest version!

Now it connects, even on localhost (problem #24 seems resolved), but when I click refresh I get:

Element with id 72 is already registered

Also:

• it places closed issues in the "Closed Issues" pane, but they are badly formatted
• the "Open Issues" pane is empty
• I looked for logs but couldn't find any

What could be the problem?

It'd be nice if this extension could just use .vscode/settings.json file instead of using it's own folder.
That'd also enable some of the default configs to be stored globally, fir example the token and domain, whilst still allowing project specific overwrites.

I understand that extensions for Codium are held at open-vsx.org rather than the Microsoft repository. Looking on that site this extension is not there. Any chance of uploading it?

p.s. I am also looking forward to the "close issue" button

With the last commit 858b8b7 I've changed the design of the items in the tree view. Before this commit the tree view offered little icons and following format:

#{issueId} - {issueTitle}

Hi, and thanks for creating this extension :)

I would be very interested in support for RemoteSourceProvider for this extension. This would ideally allow searching for repositories on the gitlab instance while checking them out. I'd be okay with adding this myself, though I have zero experience writing VSCode extensions, so it might be pretty crudely implemented 😅

In the docs it says:

Also do not push the .vscode folder to your repository and doublecheck this part. It contains your gitea server instance key.

Unfortunately committing config to the repo is standard practice. So this would be a problem for many.

There are two options:

• update docs to say that the gitea token can be kept in "User config" (which is typically not added to source control), but cannot be kept in "Workspace config" (which is).
• [better] add a feature for loading the token from a file, e.g. .vscode/gitea-vscode - this file would be added to .gitignore but the config can be committed to source control as usual

I have the following configuration data:

settings.json

• Tried http & https both.

Gitea Accessible from Browser

Error on clicking refresh

In Past, Gitea CLI write/read got accessible after this command when I first time started using Gitea.

git config --global http.sslVerify false

This extension looks really very promising indeed. Yet, I am not getting to see the issues or anything. Instead, I am presented with a rather generic "HTTP Error" message. The issue for me may be that I have Gitea running on a sub-path as root, i.e. an address like https://myservername.com/gitea. Running with code --verbose it tells me that the configuration cannot be read if I put the /gitea part in the domain name configuration. If I make it a part of the repository configuration (like gitea/myorg/myrepo) I get a 404. Is there any way to get such a setup too work?

The Refresh icon in the GITEA-ISSUES pane generates an "INVALID tree item" error for each issue in the repository, and the pane is not populated with any issues.

Caused by test for TreeItem validation introduced three months ago microsoft/vscode@43974d1.

Can be fixed by assigning c.id = c.id.toString() in

Using Gitea v1.17.2, VSCode 1.72.0

Browsing this repository after a while now I can see that there is a lot of redundant code we don't really need because the logic is almost the same at every location (i. e. the issueProvider)

Simplify the closed and openIssueProvider with interfaces.