Open
Conversation
Curently the GiteaStatus plugin only works for legacy inputs, as it attempts to read repository metadata from the `jobsetevalinput`s (which I don’t think can be set for flakes). This Commit adds support for many gitea instances by checkng whether the domain is hosting gitea. This is done by querying the /api/swagger endpoint, as that is a small static page that contains “Gitea” even when the instance has been renamed. [Gitea instances that are hosted in a subfolder](https://docs.gitea.io/en-us/reverse-proxies/#nginx-with-a-sub-path) are not supported.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebased PR of #1232
Curently the GiteaStatus plugin only works for legacy inputs, as it attempts to read repository metadata from the
jobsetevalinputs (which I don’t think can be set for flakes).This Commit adds support for many gitea instances by checkng whether the domain is hosting gitea. This is done by querying the /api/swagger endpoint, as that is a small static page that contains “Gitea” even when the instance has been renamed.
Gitea instances that are hosted in a
subfolder are not supported.