quarto-dev / quarto-dev/quarto-cli
Allow to use other Git hosts for "GitHub Links"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
As highlighted in the discussion below, it would be great to allow users to use GitLab, BitBucket, Gitea, for the "GitHub Links", and not only GitHub.
Discussed in https://github.com/quarto-dev/quarto-cli/discussions/5281
Originally posted by christophsax April 23, 2023
In Quarto, there is the lovely feature that directly links to the edit page on GitHub. At first glance, this seems to work for other platforms, such as Gitea, as well. However, quarto points to edit, Gitea expects it at _edit.
Is there any way the edit link can be tweaked?
This is where Quarto links to: .../edit/main/index.qmd
This is how a Gitea edit link looks like: .../_edit/main/index.qmd
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with discussion 5281 and the existing “GitHub Links” entry point that builds edit URLs; the payload names no source file or test. Compare the URL conventions described for GitLab, BitBucket, and Gitea. Done means users can use those hosts, including Gitea’s _edit path rather than only GitHub’s edit path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100