Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Repo: eventing-github #223

Closed
10 tasks done
lionelvillard opened this issue Aug 19, 2020 · 3 comments
Closed
10 tasks done

New Repo: eventing-github #223

lionelvillard opened this issue Aug 19, 2020 · 3 comments

Comments

@lionelvillard
Copy link
Member

lionelvillard commented Aug 19, 2020

Use this issue type to request a new repo in knative-sandbox (or
knative, which may require additional discussion).

Repo information

Org: knative-sandbox

Repo: eventing-github

Purpose (Description): Github integration with Knative Eventing

Sponsoring WG: Eventing and Source WGs

Actions to fulfill

This area is used for the TOC to track the repo creation
process

  • Add this issue to the TOC project board for review.

  • Send a PR adding entries for this repo in /peribolos/knative-sandbox.yaml

    • Add the repository and a description.
    • Grant Knative Admin the admin privilege.
    • Grant the sponsoring WG the write privilege.

Once the TOC has approved the above, it will merge and Peribolos will create an empty repository.

  • (golang) Send a PR to add aliases for knative.dev/$REPONAME import paths (sample).

  • Have a lead from the sponsoring WG bootstrap the Git repository by pushing an
    appropriate "template" repository (basic,
    sample-controller,
    sample-source) to the new repository as
    a git remote. For example:

      git clone https://github.com/knative-sandbox/sample-controller.git
      cd sample-controller
      git remote add newrepo https://github.com/knative-sandbox/$REPONAME.git
      git push newrepo master
  • Set up test-infra following the
    docs linked at the beginning.

  • Create a sample PR to verify Prow (e.g. edit the boilerplate README)

Once Prow has been verified.

  • Have a member of the TOC enable branch protections so that tide is a required presubmit check.
@mattmoor
Copy link
Member

mattmoor commented Sep 9, 2020

edited above to avoid confusion.

chaodaiG pushed a commit to chaodaiG/community that referenced this issue Sep 15, 2020
@lionelvillard
Copy link
Member Author

@grantr can you enable branch protection?

@mattmoor
Copy link
Member

I did it.

🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants