Implement events support for Forgejo by mynk8 · Pull Request #2852 · packit/packit-service

mynk8 · 2025-09-24T13:42:15Z

TODO:

Write new tests or update the old ones to cover new functionality.
Update doc-strings where appropriate.

Merge before/after

Fedora 43 release

RELEASE NOTES BEGIN

Add forgejo event support pr.Action, pr.Comment, issue.Comment, push.Commit in `events.

RELEASE NOTES END

gemini-code-assist · 2025-09-24T13:42:36Z

Summary of Changes

Hello @mynk8, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly expands the service's compatibility by adding full support for Forgejo, a self-hosted Git service. It enables the system to receive, parse, and react to various Forgejo events, such as pull request actions, issue comments, and code pushes, and to report statuses back to Forgejo repositories. This integration broadens the range of Git platforms the service can interact with.

Highlights

Forgejo Event Support: Introduced comprehensive support for Forgejo events, including pr.Action, pr.Comment, issue.Comment, and push.Commit.
New Webhook Endpoint: Added a dedicated /forgejo webhook endpoint to process incoming Forgejo events, complete with signature validation.
Event Parsing and Handling: Implemented new event classes and parsing logic specifically for Forgejo pull requests, issue comments, and push events, ensuring proper discrimination from GitHub events.
Status Reporting Integration: Integrated Forgejo into the status reporting mechanism, allowing the service to set commit statuses on Forgejo projects.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist · 2025-09-24T13:44:11Z

Summary of Changes

Hello @mynk8, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly expands the platform's compatibility by adding full event support for Forgejo, a free, open-source, community-driven forge. It introduces the necessary infrastructure to listen for, parse, and react to various events from Forgejo repositories, including pull request activities, issue comments, and code pushes. This integration allows the system to seamlessly interact with projects hosted on Forgejo, mirroring the functionality already available for other Git platforms.

Highlights

Forgejo Event Support: Introduced comprehensive support for Forgejo events, enabling the system to process pull request actions, pull request comments, issue comments, and push events from Forgejo repositories.
New Webhook Endpoint: Added a dedicated /forgejo webhook endpoint to receive and process events originating from Forgejo instances, including signature validation.
Event Parsing Logic: Implemented new parser methods (parse_forgejo_push_event, parse_forgejo_pr_event, parse_forgejo_comment_event) to correctly interpret Forgejo webhook payloads and convert them into internal event objects.
Status Reporting Integration: Integrated Forgejo into the status reporting mechanism, allowing the system to set commit statuses on Forgejo pull requests and commits, and handle API exceptions gracefully by adding comments.
Abstract Event Classes: Created Forgejo-specific event classes (ForgejoEvent, pr.Action, pr.Comment, issue.Comment, push.Commit) to encapsulate the structure and data of various Forgejo events.
GitHub Event Parser Refinement: Modified existing GitHub event parsers to explicitly skip events originating from Forgejo, preventing misinterpretation and ensuring proper event routing.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request introduces support for Forgejo events, including a new webhook endpoint, event classes, and parsing logic. The implementation is comprehensive, covering PR actions, comments, and pushes. I've identified a couple of critical issues that will cause runtime errors, related to undefined variables in the new webhook endpoint. Additionally, there are opportunities to improve performance by passing more data during event instantiation to avoid later API calls, and to enhance robustness by using a more reliable method for distinguishing Forgejo events. I've also included some minor suggestions for code style and consistency.

packit_service/service/api/webhooks.py

packit_service/worker/parser.py

packit_service/events/__init__.py

packit_service/events/forgejo/__init__.py

packit_service/events/forgejo/issue.py

packit_service/service/api/webhooks.py

packit_service/worker/parser.py

tests/unit/events/test_forgejo.py

mynk8 · 2025-09-24T13:44:40Z

Would like to ask, Is there an alternative to mocking the Project object from ServiceConfig?

softwarefactory-project-zuul · 2025-09-24T13:44:46Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/6b5bcc3940824c859878528bdb9fabf3

❌ pre-commit FAILURE in 1m 52s
❌ packit-service-tests FAILURE in 1m 18s

gemini-code-assist

Code Review

This pull request introduces support for Forgejo events, including pull requests, issue comments, and pushes. It adds new event classes, a webhook endpoint, and parsers for Forgejo payloads. The implementation is comprehensive, with new logic for handling Forgejo's specific event structure and new tests to cover the functionality. My review focuses on a few critical issues, such as missing variable definitions that would cause runtime errors, and some suggestions for improving the robustness and maintainability of the event parsing logic.

packit_service/service/api/webhooks.py

packit_service/events/forgejo/issue.py

packit_service/worker/parser.py

softwarefactory-project-zuul · 2025-09-24T14:18:40Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/d1ca51a8543b4c02ba84542cb2b1885c

❌ pre-commit FAILURE in 1m 52s
❌ packit-service-tests FAILURE in 2m 36s

gemini-code-assist

Code Review

This pull request introduces support for Forgejo webhooks, including events for pull requests, issues, and pushes. The implementation includes new event classes, a webhook endpoint, and parsing logic. The changes are well-structured and include comprehensive tests.

I've found a critical security vulnerability where the Forgejo webhook signature is not being validated, and another high-severity issue with incomplete validation logic. I've also pointed out a medium-severity issue regarding redundant code in the event parser.

My review comments provide suggestions to fix these issues. Once addressed, this will be a great addition.

packit_service/service/api/webhooks.py

packit_service/worker/parser.py

softwarefactory-project-zuul · 2025-09-24T14:31:51Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/d23cb3da42f54738b58c59a6df0e98c9

✔️ pre-commit SUCCESS in 1m 55s
✔️ packit-service-tests SUCCESS in 4m 04s

softwarefactory-project-zuul · 2025-09-24T14:49:21Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/0b422d245d504b979839d296ec99c1c9

✔️ pre-commit SUCCESS in 1m 58s
✔️ packit-service-tests SUCCESS in 3m 51s

softwarefactory-project-zuul · 2025-09-24T14:59:18Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/66dbb8c8e7e74e1f9e941684df568efd

✔️ pre-commit SUCCESS in 1m 55s
✔️ packit-service-tests SUCCESS in 3m 42s

betulependule · 2025-10-10T08:52:18Z

This is probably just a nitpick, but this docstring should probably be edited to mention Forgejo webhooks, not just GitHub and GitLab. I would just add Forgejo inside the brackets so that it says: (GitHub/GitLab/Forgejo webhook).

packit-service/packit_service/worker/parser.py

Lines 97 to 101 in ee1c350

    
           class Parser: 
        
               """ 
        
               Once we receive a new event (GitHub/GitLab webhook) for every event 
        
               we need to have method inside the `Parser` class to create objects defined in `event.py`. 
        
               """

mfocko

Apart from the commit history and some minor issues, looks OK to me :)

mfocko · 2025-10-10T13:40:44Z

packit_service/events/abstract/comment.py

        tag_name: str = "",
        comment_object: Optional[Comment] = None,
        dist_git_project_url=None,
+        commit_sha: Optional[str] = None,


How come this got in:

include unit tests for forgejo event; fixes

😄

mfocko · 2025-10-10T13:41:44Z

packit_service/events/forgejo/abstract.py

 class ForgejoEvent(ForgeIndependent):
    def __init__(self, project_url: str, pr_id: Optional[int] = None, **kwargs):
-        super().__init__(pr_id=pr_id)
+        super().__init__(pr_id=pr_id, **kwargs)


Why? Just an FYI, this can cause issues.

that was so that I could pass actor and other parameters into the event, not anymore. corrected it.

mfocko · 2025-10-10T13:45:39Z

packit_service/events/forgejo/pr.py

-        self.commit_sha_before = commit_sha_before
-        self.actor = actor
-        self.identifier = str(pr_id)
-        self._pr_id = pr_id
-        self.git_ref = None  # use pr_id for checkout


Are you sure about removing all of these? You left the arguments in the constructor, but you do not use them.

packit_service/service/api/webhooks.py

packit_service/worker/parser.py

mfocko · 2025-10-10T14:13:35Z

packit_service/worker/parser.py

+                "description", "visibility", "followers_count", 
+                "following_count", "starred_repos_count", "username"
+            }
+            return any(field in user_obj for field in forgejo_fields)


Since you're using any, I assume those are the Forgejo-unique fields?

mfocko · 2025-10-10T14:33:19Z

packit_service/worker/parser.py

            logger.warning("No event to process!")
            return None

+        # Check if this is a Forgejo event and prioritize Forgejo parsers


I don't like this… This would make sense, if majority of the events would come from Forgejo instances; this way you are basically putting Forgejo at the top¹, so it gets prioritised overall…

The best way would be for us to collect metrics on what we parse and sort it from most frequent to least frequent events… I'll probably open up a follow-up issue for this, it could definitely help with SLO1 and responsiveness issues we've been having recently.

Cc @packit/the-packit-team
Related to #2854

Footnotes

at least there's that one helper _is_forgejo_event(), but when you get bunch of events, it will add up… ↩

Yes, I am also confused by the need to prioritise Forgejo parsers in particular.

The structure of webhook payload was similar to that of github, some events would mistakenly get passed as github objects, in tests as well. I think the logic is wrong to fix that and maybe determine the type of forge from the HTTP headers at service level instead? but that would break tests and I think not the best way out.

I see. If we don't find a better way to solve this, there should probably be a comment added to explain why the Forgejo parsers are being prioritized so that it's clear in the future. @mfocko, what do you think?

Looking at it again, I think it would be better to detect that the event in a Forgejo event in the Github parsers and handle it there. The code would be cleaner without having to prioritize Forgejo events. I'll take further look into this.

It's possible we will be using Fedora messaging bus (instead of a webhook) to receive Forgejo events. If so, then parsing of Forgejo events will be done a bit different (similar to Pagure events). It should be possible to identify Forgejo events based on the content of event.topic inside the parsers (in case Fedora messaging bus ends up being used). Before making changes to this, I'll wait on further information on what ends up being used to receive the events.

packit_service/worker/parser.py

packit_service/events/forgejo/__init__.py

betulependule

Overall, it looks good to me so far. I didn't find any other issues other than what @mfocko has pointed out already. Just regarding the tests, it would be good for consistency to add ForgejoService in this conftest.py file.

packit-service/tests/conftest.py

Lines 28 to 46 in aa1ffde

    
           @pytest.fixture(autouse=True) 
        
           def global_service_config(): 
        
               """ 
        
               This config will be used instead of the one loaded from the local config file. 
        
               You can still mock/overwrite the service config content in your tests 
        
               but this one will be used by default. 
        
               You can also (re)define some values like this: 
        
               ServiceConfig.get_service_config().attribute = "value" 
        
               """ 
        
               service_config = ServiceConfig() 
        
               service_config.fas_user = "packit" 
        
               service_config.services = { 
        
                   GithubService(token="token"), 
        
                   GitlabService(token="token"), 
        
                   PagureService(instance_url="https://src.fedoraproject.org", token="token"), 
        
                   PagureService(instance_url="https://git.stg.centos.org", token="6789"), 
        
               }

packit_service/service/api/webhooks.py

softwarefactory-project-zuul · 2025-10-21T12:55:35Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/a5f71bf636474e5290baeddc51fd4400

❌ pre-commit FAILURE in 1m 12s
❌ packit-service-tests FAILURE in 5m 24s

softwarefactory-project-zuul · 2025-10-21T15:14:29Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/f90eedd8e9f947c4b77d42d5d3c4cacd

❌ pre-commit FAILURE in 1m 11s
✔️ packit-service-tests SUCCESS in 4m 29s

mynk8 · 2025-10-21T15:23:17Z

my bad. rebasing...

softwarefactory-project-zuul · 2025-10-21T15:29:02Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/10df47ce2d4f47e683b2fedfa6784f6c

❌ pre-commit FAILURE in 1m 10s
✔️ packit-service-tests SUCCESS in 6m 10s

softwarefactory-project-zuul · 2025-10-21T15:53:33Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/5a29721b13f74ab0b8c05e078e7904cb

❌ pre-commit FAILURE in 1m 11s
✔️ packit-service-tests SUCCESS in 5m 05s

softwarefactory-project-zuul · 2025-10-21T16:06:44Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/a9ee7e09b9734fb19b03c8baf06172c7

❌ pre-commit FAILURE in 1m 09s
❌ packit-service-tests FAILURE in 5m 03s

softwarefactory-project-zuul · 2025-10-21T16:46:40Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/da444339ea33421198595bc6c0847b35

❌ pre-commit FAILURE in 1m 08s
❌ packit-service-tests FAILURE in 4m 48s

mynk8 · 2025-10-21T17:03:46Z

pre-commit tests failing due to:

An unexpected error has occurred: CalledProcessError: command: ('/home/zuul-worker/.cache/pre-commit/repo5ifl3exm/node_env-default/bin/node', '/home/zuul-worker/.cache/pre-commit/repo5ifl3exm/node_env-default/bin/npm', 'install', '--include=dev', '--include=prod', '--ignore-prepublish', '--no-progress', '--no-save')
return code: 127
stdout: (none)
stderr:
    /home/zuul-worker/.cache/pre-commit/repo5ifl3exm/node_env-default/bin/node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Check the log at /home/zuul-worker/.cache/pre-commit/pre-commit.log

and tests due to problem communicating with pagure. for

FAILED tests/unit/events/test_koji.py::test_parse_koji_build_event_start_old_format
FAILED tests/integration/test_dg_commit.py::test_precheck_koji_build_push_pr[packit-allowed_pr_authors0-True]

majamassarini · 2025-10-27T08:53:40Z

recheck

softwarefactory-project-zuul · 2025-10-27T09:00:09Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/d7fcf14f9b0c496ea722a8f1f4f32b25

✔️ pre-commit SUCCESS in 1m 50s
❌ packit-service-tests FAILURE in 5m 49s

mynk8 · 2025-10-30T05:35:22Z

recheck

softwarefactory-project-zuul · 2025-10-30T05:42:56Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/628a29c8b32f4478a6d03ee236a4dca6

✔️ pre-commit SUCCESS in 1m 49s
✔️ packit-service-tests SUCCESS in 6m 55s

softwarefactory-project-zuul · 2025-10-30T05:48:43Z

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/48d54d3f528141a7a4a3fe6cf3dfab97

✔️ pre-commit SUCCESS in 1m 46s
❌ packit-service-tests FAILURE in 4m 40s

mynk8 · 2025-10-30T06:53:09Z

recheck

mynk8 · 2025-10-30T06:54:42Z

wait, didn't notice till now but some tests are randomly failing due to Pagure returning a 503

FAILED tests/unit/test_checkers.py::test_run_condition[JobType.koji_build-JobConfigTriggerType.commit-koji_build_retrigger_pr_comment-None-True-False]
FAILED tests/unit/test_checkers.py::test_run_condition[JobType.koji_build-JobConfigTriggerType.commit-koji_build_retrigger_pr_comment-None-True-True]

softwarefactory-project-zuul · 2025-10-30T06:59:21Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/6aa7a34c40274e79990223bf781e5ac8

✔️ pre-commit SUCCESS in 1m 47s
✔️ packit-service-tests SUCCESS in 5m 31s

softwarefactory-project-zuul · 2025-11-17T08:46:03Z

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/fd42e4a9446a4a4b96c414df043fc11f

✔️ pre-commit SUCCESS in 1m 49s
✔️ packit-service-tests SUCCESS in 3m 52s

betulependule · 2026-01-28T13:19:38Z

Hi @mynk8, thank you for all of the work. May ask you whether this is something you plan to continue working on? If not, do we have your permission to finish this PR? This functionality would be great to have.

mynk8 · 2026-01-28T13:30:07Z

Hi @mynk8, thank you for all of the work. May ask you whether this is something you plan to continue working on? If not, do we have your permission to finish this PR? This functionality would be great to have.

I'd like to help with the PR, but I've been out of touch with the codebase for a while. Please feel free to finish it if that's more convenient. Thanks!

betulependule · 2026-01-29T09:05:52Z

I'd like to help with the PR, but I've been out of touch with the codebase for a while. Please feel free to finish it if that's more convenient. Thanks!

Thank you for responding. In that case we will continue work on this soon. If you want, you are welcome to drop in at any time before it is finished. Thanks again.

centosinfra-prod-github-app · 2026-02-03T10:56:56Z

Build failed.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/f62ceefd14354d62a42b66c401899bea

❌ pre-commit FAILURE in 1m 50s
❌ packit-service-tests FAILURE in 1m 13s

@gemini-code-assist

Update packit_service/worker/reporting/reporters/base.py Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Update packit_service/service/api/webhooks.py Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Update packit_service/worker/parser.py Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Update packit_service/events/forgejo/pr.py Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> pre-commit and mypy fixes test(data): add Forgejo webhooks for tests include unit tests for forgejo event; fixes add check for prioritising Forgejo before parsing events; fixes pre-commit remove redundant entries in parser list; fix bug Apply suggestion from @gemini-code-assist[bot] Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> implement validate_token for ForgejoWebhooks; correct the pr.Action impl for Forgejo; fix a problem in parser that could have caused keynotfound errors. implement validate_token for ForgejoWebhooks; correct the pr.Action impl for Forgejo; fix a problem in parser that could have caused keynotfound errors. Implement Forgejo event handling in Packit Service.

centosinfra-prod-github-app · 2026-02-03T11:08:38Z

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/b84df266791a4b46920eafa4cae97522

✔️ pre-commit SUCCESS in 1m 49s
✔️ packit-service-tests SUCCESS in 3m 29s

mynk8 requested a review from a team as a code owner September 24, 2025 13:42

usercont-release-bot added this to Packit Kanban Board Sep 24, 2025

github-project-automation bot moved this to new in Packit Kanban Board Sep 24, 2025

mynk8 changed the title ~~Rebase/forgejo~~ Implement events support for Forgejo Sep 24, 2025

gemini-code-assist bot reviewed Sep 24, 2025

View reviewed changes

packit_service/service/api/webhooks.py Show resolved Hide resolved

packit_service/events/forgejo/issue.py Outdated Show resolved Hide resolved

packit_service/worker/parser.py Outdated Show resolved Hide resolved

packit_service/worker/parser.py Show resolved Hide resolved

gemini-code-assist bot reviewed Sep 24, 2025

View reviewed changes

packit_service/service/api/webhooks.py Show resolved Hide resolved

packit_service/service/api/webhooks.py Show resolved Hide resolved

packit_service/worker/parser.py Outdated Show resolved Hide resolved

TomasTomecek assigned mfocko and betulependule Oct 6, 2025

gotmax23 mentioned this pull request Oct 10, 2025

Support Forgejo for upstream CI #2855

Open

5 tasks

mfocko reviewed Oct 13, 2025

View reviewed changes

betulependule reviewed Oct 16, 2025

View reviewed changes

packit_service/service/api/webhooks.py Show resolved Hide resolved

mynk8 force-pushed the rebase/forgejo branch from 02732fe to 714dcd6 Compare October 21, 2025 16:00

mynk8 force-pushed the rebase/forgejo branch from 66257c5 to 0717436 Compare October 21, 2025 16:41

betulependule force-pushed the rebase/forgejo branch from 7d5e9dc to 3a9b15c Compare February 3, 2026 10:54

usercont-release-bot added this to Packit pull requests Feb 3, 2026

github-project-automation bot moved this to New in Packit pull requests Feb 3, 2026

mynk8 and others added 3 commits February 3, 2026 12:03

Implement Forgejo event handling in Packit Service

fb9033f

test(data): add Forgejo webhooks for tests

c975387

betulependule force-pushed the rebase/forgejo branch from 3a9b15c to 7182065 Compare February 3, 2026 11:04

	@pytest.fixture(autouse=True)
	def global_service_config():
	"""
	This config will be used instead of the one loaded from the local config file.

	You can still mock/overwrite the service config content in your tests
	but this one will be used by default.

	You can also (re)define some values like this:
	ServiceConfig.get_service_config().attribute = "value"
	"""
	service_config = ServiceConfig()
	service_config.fas_user = "packit"
	service_config.services = {
	GithubService(token="token"),
	GitlabService(token="token"),
	PagureService(instance_url="https://src.fedoraproject.org", token="token"),
	PagureService(instance_url="https://git.stg.centos.org", token="6789"),
	}

Conversation

mynk8 commented Sep 24, 2025

Uh oh!

gemini-code-assist bot commented Sep 24, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot commented Sep 24, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mynk8 commented Sep 24, 2025

Uh oh!

softwarefactory-project-zuul bot commented Sep 24, 2025

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

softwarefactory-project-zuul bot commented Sep 24, 2025

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

softwarefactory-project-zuul bot commented Sep 24, 2025

Uh oh!

softwarefactory-project-zuul bot commented Sep 24, 2025

Uh oh!

softwarefactory-project-zuul bot commented Sep 24, 2025

Uh oh!

betulependule commented Oct 10, 2025

Uh oh!

mfocko left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Footnotes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mynk8 Oct 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mynk8 Oct 16, 2025 •

edited

Loading