NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
Would it be possible to set notifications about issues and PRs from 2 pagure repos:
issues
PRs
to go to #l10n:fedoraproject.org matrix room?
#l10n:fedoraproject.org
We have a way to republish Fedora messages on matrix in FMN, but it doesn't cover this case. @abompard Do you have idea how to solve this?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation
can't we configure nonbot-pagure for that purpose, as we do for releng and infra issues/PRs?
Maybe I just misunderstood what is possible from Infra & RelEng Update – Week 4 2024:
Updates Nonbot now is notifying on pagure repos (new issues and git pushes). This was done previously with a generic maubot webhook plugin, but now uses a pagure-specific plugin. This has the benefit of being able to notify any room about any pagure repo. Additionally, the old generic way was not checking if messages were coming from pagure, now it verifies against the pagure webhook key.
Updates
Nonbot now is notifying on pagure repos (new issues and git pushes). This was done previously with a generic maubot webhook plugin, but now uses a pagure-specific plugin. This has the benefit of being able to notify any room about any pagure repo. Additionally, the old generic way was not checking if messages were coming from pagure, now it verifies against the pagure webhook key.
I have tried to find a way to set this in FNM, but failed. I was surprised, for example, that a pagure repo, of which I'm an admin, wasn't available for my username. But maybe there needs to be some matching between fas user/gropu and pagure user/group...
I do not know, but I will definitely appreciate any help with this.
I think I can set that up, but it would require the configuration of a webhook URL on the pagure repositories, and then providing me the private web-hook key for each repo (I don't have admin access to any of those repositories).
I have only for pagure.io/fedora-l10n/tickets.
And I was thinking initially about a notification on issue created and maybe issue closed.
issue created
issue closed
I guess for pagure.io/fedora-l10n/docs we need to ping @jibecfed.
notification for new issue has been set up for pagure.io/fedora-l10n/tickets. For PRs, we need to update the plugin to allow the pull-request.new topic.
pull-request.new
IMHO, it would be welcome by the whole Fedora Community if thepull-request topic is implemented.
pull-request
Just my 2c.
PR here
@ryanlerch can you take a look?
Hi team,
I modified this Pagure group to ease administration, this is for Localization Admins: https://pagure.io/group/fedora-l10n
Members of this group are admins on the l10n projects
We should probably do the same for all these projects: https://pagure.io/projects/fedora-docs-l10n/%2A Does infra team can modify all these 51 projects to add fedora-l10n group as admin?
Note, there already is a group to allow commits (for direct commits from weblate or maintainers), https://pagure.io/group/fedora-docs-l10n
I think @ryanlerch might have a script for this? Otherwise we will need to create one...
fedora-l10n/tickets and fedora-l10n/docs are now configured to send on new issues and new PRs.
@darknao thanks for the PR over on the plugin (its been merged and deployed, and working now).
Metadata Update from @ryanlerch: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.