New Repo: actions-kind - Githubissues

n3wscott commented 4 years ago

Repo information

Org: knative-sandbox

Repo: actions-kind

Purpose (Description): GitHub Action to bundle our logic for performing kind based e2e testing.

Sponsoring WG: Productivity

Actions to fulfill

This area is used to track the repo creation process. The requestor and sponsoring WG lead should perform the steps listed below and cross out the checkmarks when done. The TOC is involved only in the TOC Gate steps.

[x] Add this issue to the TOC project board for review.

You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the Add cards interface.

[x] Send a PR adding entries for this repo in /peribolos/knative-sandbox.yaml. Please mind the alphabetical order when adding to a list. https://github.com/knative/community/issues/325
- [x] Add the repository and a description.
- [x] Grant Knative Admin the admin privilege.
- [x] Grant the sponsoring WG the write privilege.

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

[x] (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)

TOC Gate : Once Prow has been verified

[ ] Have a member of the TOC enable branch protections so that tide is a required presubmit check.

evankanderson commented 4 years ago

This is lined up with downstream-test, but not with e.g. net-*.

evankanderson commented 4 years ago

We may want to change these to be a common prefix going forward so that they collate together. If these are specifically github actions, we may want to prefix actions-*

n3wscott commented 4 years ago

I like actions-* and I can followup with a rename of downstream-test -> actions-downstream

Update: dropped the -test from actions-downstream-test

n3wscott commented 4 years ago

peribolos pr has been updated to use the name actions-kind

n3wscott commented 4 years ago

Updated https://github.com/knative/community/pull/325 and rebased, actions- is now in play.

mattmoor commented 3 years ago

/assign @evankanderson

evankanderson commented 3 years ago

(I think you have write access for pushing the repo now, which would be the next step if this is still needed.)

mattmoor commented 3 years ago

/assign @n3wscott

Scott, are you still pursuing this?

n3wscott commented 3 years ago

We should. I can. I was several more actions repos

markusthoemmes commented 3 years ago

Anything left here? Seems like the repo exists.

evankanderson commented 2 years ago

It looks like there's been no further activity on this repo? Do we need to do more here, particularly since it's possible to have mulitple actions in one repo if you're okay with them being versioned together?

rhuss commented 2 years ago

We don't need a repo, but want to use reusable workflows --> https://docs.github.com/en/actions/using-workflows/reusing-workflows#creating-a-reusable-workflow

knative / community

New Repo: actions-kind #324

Repo information

Actions to fulfill