When using the GitHub Organization Folder against my own GitHub account, I would like to be able to only include repositories that I have created, not just forks.

      For example, if I fork a Jenkins plugin to submit a patch, all of a sudden there's a new Pipeline building on my local Jenkins.

      I think ti would be ideal to support excluding all forks with a checkbox in the folder configuration

          [JENKINS-37939] Provide the option to exclude forks

          Michael Neale added a comment -

          The problem I see is people turning this on, and then wondering why pipelines dont' show up (plenty of people work off forks, but I think primarily in OSS).

          I would like to think of what is the default: could the default be to not add forks as pipelines? If so, then I think this is a good idea (and the checkbox be to turn it on).

          Michael Neale added a comment - The problem I see is people turning this on, and then wondering why pipelines dont' show up (plenty of people work off forks, but I think primarily in OSS). I would like to think of what is the default: could the default be to not add forks as pipelines? If so, then I think this is a good idea (and the checkbox be to turn it on).

          This is an ideal candidate for an extension plugin. An SCMSourceFilterTrait is all that is required (would need to be github specific though)

          Stephen Connolly added a comment - This is an ideal candidate for an extension plugin. An SCMSourceFilterTrait is all that is required (would need to be github specific though)

          The lack of such option becomes exceptionally painful in a situation where the organization has a lot of repositories and one or two forks that we really don't want to build. We deal using a repository name regex, but it's a PITA to maintain.

          Margaret Lewicka added a comment - The lack of such option becomes exceptionally painful in a situation where the organization has a lot of repositories and one or two forks that we really don't want to build. We deal using a repository name regex, but it's a PITA to maintain.

            cloudbees CloudBees Inc.
            rtyler R. Tyler Croy
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: