feat: Codeberg API #1836
Open
feat: Codeberg API #1836
+15
−0
Conversation
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
|
To open the tree, its 'o' from the status buffer (main neogit buffer) and to open the commit, its 'o' from the commit view. I suppose that could be better documented. |
|
Thanks! I now tested all three. Btw, typos detected two mispellings in code other than mine: |
|
And one thing I noticed in the doc which is not necessarily a typo, but surely a grammar error, is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #1664. Codeberg uses ForgeJo's API, which is only slightly different from M$ GitH*b's:
https://codeberg.org/api/swagger#/repository
Observe that ForgeJo can be freely selfhosted, so the same config could also scale to arbitrary ForgeJo instances in the future.
I ran
make test,make lint, andstylua ..I tested the "open pull request" feature, but I could not find the commands to open the commit/branch tree on the web, despite reading the README. Can somebody help me test those two out, too, before the merge, please?