jenkinsci / jenkinsci/github-branch-source-plugin

[JENKINS-66608] Exclude internal repositories

Open
#1,374 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:github-branch-source-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
218
Forks
399
Avg merge
30m
Merged PRs (30d)
1

Description

Github has added new repository types in the last year and it would be nice to be able to filter them out during repository discovery in a Github org folder.  We do not want to include "internal" repositories in our org scan as these can contain Jenkinsfiles but are not intended to be built.  This was not an issue previously because we used service accounts and repository access management, but "internal" repositories are visible to all members of the github org.

 

This is somewhat related to and possibly resolved by this PR: 

https://github.com/jenkinsci/github-branch-source-plugin/pull/344

 

I believe a graphql query could filter out internal repositories.


Originally reported by dkallman, imported from: Exclude internal repositories
  • status: Open
  • priority: Minor
  • component(s): github-branch-source-plugin
  • label(s): plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-02
Raw content of original issue

Github has added new repository types in the last year and it would be nice to be able to filter them out during repository discovery in a Github org folder.  We do not want to include "internal" repositories in our org scan as these can contain Jenkinsfiles but are not intended to be built.  This was not an issue previously because we used service accounts and repository access management, but "internal" repositories are visible to all members of the github org.

 

This is somewhat related to and possibly resolved by this PR: 

https://github.com/jenkinsci/github-branch-source-plugin/pull/344

 

I believe a graphql query could filter out internal repositories.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with repository discovery in a GitHub org folder and review the related pull request #344 mentioned in the issue. Check how the GitHub query handles repository types; done means internal repositories are excluded from organization scans without excluding other intended repositories.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.