Skip to content

[WIP]: implement ForgeJo/Codeberg support #1224

Draft
Shadow53 wants to merge 13 commits into
GothenburgBitFactory:developfrom
Shadow53:gitea-forgejo
Draft

[WIP]: implement ForgeJo/Codeberg support #1224
Shadow53 wants to merge 13 commits into
GothenburgBitFactory:developfrom
Shadow53:gitea-forgejo

Conversation

@Shadow53

@Shadow53 Shadow53 commented Jul 3, 2026

Copy link
Copy Markdown

This is a reopening on #1048 since it got closed by the original author.

I have not made any changes other than cherry-picking commits, nor have I tested things yet. I will edit this post once I have time to test things and make any necessary changes.

Since it has been two years since the previous PR was reviewed, I'd appreciate a fresh review on this PR. I'll try to apply any open comments from that PR here, though.

wamsachel and others added 8 commits July 3, 2026 00:16
Builds off PR GothenburgBitFactory#720 to add gitea integration to bugwarrior.
mish-mash between the github and gitlab documentation with everything I
don't think is supported removed.
Remove user+pass auth, token only now.
Added issue API Querying for writing custom queries
Added include_assigned,created,mentioned, and review_requested issues
config settings
Added ability to limit the number of issues you will query (Gitea limits
the API by default to 50, but I host my own instance so I raised it)
get_tags simplified greatly
@Lotram

Lotram commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

Hi, maybe @ryneeverett will have another opinion, as the main maintainer, but I think you should first implement some tests and comply with formatting / linting rules from this repo (basically ensure all CI jobs are green) before we properly review this PR.

As you're starting over for this, I would also suggest you squash all commits

@Shadow53

Copy link
Copy Markdown
Author

I think you should first implement some tests and comply with formatting / linting rules ... before we properly review this PR.

Doing my best there. Just pushed my current state, which is an added test file with failing tests. I don't understand what's causing this error though. Have I missed updating a specific file?

ValueError: Configured service 'forgejo' not found. Is it installed? Or misspelled?

I will be working on fixing the various ValidationErrors, though.

As you're starting over for this, I would also suggest you squash all commits

I'm accustomed to squashing commits as part of merging. If you don't squash in this repo, I can definitely squash the old commits.

@Shadow53 Shadow53 changed the title [WIP]: implement Gitea/ForgeJo/Codeberg support [WIP]: implement ForgeJo/Codeberg support Jul 12, 2026
@Shadow53

Copy link
Copy Markdown
Author

Figured out the Configured service 'forgejo' not found error and have it fixed in a local commit.

@ryneeverett

Copy link
Copy Markdown
Collaborator

I typically squash new service PR's since they only ought to be one commit, so no worries on keeping the commit history clean.

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.

5 participants