Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10491

Fix wildfly-capabilities repository representation on GitHub

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Trivial Trivial
    • None
    • None
    • Documentation
    • None

      Currently, the https://github.com/wildfly/wildfly-capabilities repository says its "forked from bstansberry/wildfly-capabilities". The common practice and understanding in community is that the upstream repository is the one that is not forked from any other repository. Thus having the upstream repository not represented as upstream is confusing.

      To remedy this, with a method we used in the past, is to delete the bstansberry/wildfly-capabilities repository (and then fork from wildfly of course).

      The repo should have been moved to wildfly organization and not forked. This as a result has messed up all the previous forks, like https://github.com/rhusar/wildfly-capabilities which makes a poor usability from the UI, because it opens PRs against wrong repo by default.

            rhn-engineering-rhusar Radoslav Husar
            rhn-engineering-rhusar Radoslav Husar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: