[JENKINS-71599] strategies for sub-dividing a github-org into different folders

we have historically used github-enterprise (ghe) which is more liberal about creating distinct organizations, recently our company is looking to use github.com which does not lend itself to creating many organizations. so where we once had hundreds of ghe organizations, we would now have one large github.com organization and rely on github teams to represent "sub-organizations" within the company.

currently, i am only aware of a regular/wild-card expression type match to filter repos for inclusion into a github-org.

my new feature suggestion for this plugin would be to allow for one or more alternate strategies to identify repos from an org for inclusion in a github-org construct, for instance, one obvious strategy comes to mind which is the association of a repo with a team.

another option could be regular/wild-card expression match for a string found in a particular file name (e.g. `github-org.dat`).

these would be alternate strategies for filtering repos for an org when filtering off repo name is not practical for some reason.

 

 

---
Originally reported by tony_k, imported from: strategies for sub-dividing a github-org into different folders

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

Raw content of original issue

we have historically used github-enterprise (ghe) which is more liberal about creating distinct organizations, recently our company is looking to use github.com which does not lend itself to creating many organizations. so where we once had hundreds of ghe organizations, we would now have one large github.com organization and rely on github teams to represent "sub-organizations" within the company.


currently, i am only aware of a regular/wild-card expression type match to filter repos for inclusion into a github-org.


my new feature suggestion for this plugin would be to allow for one or more alternate strategies to identify repos from an org for inclusion in a github-org construct, for instance, one obvious strategy comes to mind which is the association of a repo with a team.


another option could be regular/wild-card expression match for a string found in a particular file name (e.g. `github-org.dat`).


these would be alternate strategies for filtering repos for an org when filtering off repo name is not practical for some reason.