[JENKINS-62937] Respond to more GitHub 'Repository' actions

Right now the github-branch-source plugin responds to 'repository creation' events when an org-level webhook is delivered. This causes a rescan of the org so that if the new repository has the necessary configuration a job (or jobs) will be created for it.

There are quite a few other events which can occur in an organization that could also trigger a scan: archiving/unarchiving a repository (especially important if the trait to exclude archived repositories is in use), deletion, renaming, and possibly transferring as well.

Is there a specific reason that these other events are ignored, or is this just a situation where nobody has added support for them yet?

---
Originally reported by kpfleming, imported from: Respond to more GitHub 'Repository' actions

• status: Open
  
• priority: Minor
  
• component(s): github-branch-source-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-02
  

Right now the github-branch-source plugin responds to 'repository creation' events when an org-level webhook is delivered. This causes a rescan of the org so that if the new repository has the necessary configuration a job (or jobs) will be created for it.


There are quite a few other events which can occur in an organization that could also trigger a scan: archiving/unarchiving a repository (especially important if the trait to exclude archived repositories is in use), deletion, renaming, and possibly transferring as well.


Is there a specific reason that these other events are ignored, or is this just a situation where nobody has added support for them yet?