Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Codeberg endpoints #36

Merged
merged 5 commits into from
Jan 14, 2024
Merged

Conversation

tranzystorekk
Copy link
Contributor

Hi, I discovered spacebadgers some time ago and really liked it!

Was looking at existing endpoints and thought I could contribute a Codeberg one. The changes in this PR are heavily inspired by #14 but if there are any remarks I'll gladly apply them.

Gitea/Forgejo don't seem to track a contributor list or repo license yet, so I didn't include an endpoint for those.

Copy link

vercel bot commented Jan 13, 2024

@tranzystorekk is attempting to deploy a commit to the splittydev's Team Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Jan 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
spacebadgers ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 14, 2024 4:34pm

@SplittyDev
Copy link
Owner

Awesome, thanks!

I'll have to figure out how to obtain a Codeberg access token for the env before I can merge this..
Will test again once I have a working one!

@tranzystorekk
Copy link
Contributor Author

I'll have to figure out how to obtain a Codeberg access token for the env before I can merge this..

You can generate a token from a codeberg account via Settings -> Applications; don't forget to expand the "Select permissions" section and mark at least repository as Read

@SplittyDev
Copy link
Owner

SplittyDev commented Jan 14, 2024

Alright, I've added a Codeberg token to the preview env, let's see if everything works after redeploying

@SplittyDev
Copy link
Owner

  • Release:
  • Issues:
  • Open Issues:
  • Closed Issues:

@tranzystorekk for some reason the issues endpoints all show None for forgejo, even though they do have active open as well as closed issues. The release endpoint works correctly.

@tranzystorekk
Copy link
Contributor Author

Ah right, the issues have their own access token permission, issue

@SplittyDev
Copy link
Owner

Ah right, the issues have their own access token permission, issue

Awesome, works now! Do you wanna change anything or shall I merge?

@tranzystorekk
Copy link
Contributor Author

I'll quickly simplify the needless code in buildUrl and then it's good to go!

@tranzystorekk
Copy link
Contributor Author

OK, done! Thank you for engaging with me! 😊

@SplittyDev
Copy link
Owner

OK, done! Thank you for engaging with me! 😊

Thanks a lot for contributing this code! 🚀

@SplittyDev SplittyDev merged commit a186a1f into SplittyDev:main Jan 14, 2024
7 checks passed
@SplittyDev
Copy link
Owner

@all-contributors please add @tranzystorekk for code

Copy link
Contributor

@SplittyDev

I've put up a pull request to add @tranzystorekk! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants