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

Update actions readmes/contributing to point back to github-ospo #75

Closed
ahpook opened this issue Mar 18, 2024 · 8 comments
Closed

Update actions readmes/contributing to point back to github-ospo #75

ahpook opened this issue Mar 18, 2024 · 8 comments
Assignees
Labels
ospo-actions Issues relating to the OSPO Actions

Comments

@ahpook
Copy link
Contributor

ahpook commented Mar 18, 2024

Currently the various ospo actions are completely separate and there's not much connective "tissue" between them and the broader efforts to help OSPOs on GitHub. As a first step, we should update their READMEs to headline the rest of the tools and the github/github-ospo repo, plus indicate that PRs about the code in a specific action lives in its repo, but questions about overall usage or feature enhancements should go here instead. The actions are in:

  • github/automatic-contrib-prs
  • github/cleanowners
  • github/contributors
  • github/evergreen
  • github/issue-metrics
  • github/stale-repos
@ahpook ahpook converted this from a draft issue Mar 18, 2024
@ahpook ahpook self-assigned this Mar 18, 2024
@ahpook ahpook moved this from Backlog to In progress in GitHub OSPO OSS Board Mar 18, 2024
@ahpook ahpook added the ospo-actions Issues relating to the OSPO Actions label Mar 19, 2024
@jmeridth
Copy link
Member

@ahpook

Love the link back to this repo (helps inform users there are other GitHub Actions available)

I'm wary of the Issues being back on this repo for all the Actions. Is this for ease of centralization for product and to ensure we keep each repo in "sync" (shared techniques, etc)? I assume so.

This is not the norm for open-source contributation IMO. I'd done something else. I've created a project at the organization level (e.g., OSPO) and when issues are created in each repository we can automate assigning them to that project. Therefore product and maintainers get one location to manage issues. Still gives contributors the "normal" open-source process "feel" but allows product/maintainers to not have to go to each repository. Especially as the repository count grows.

wdyt?

@jmeridth
Copy link
Member

Looks like there is already have a project 😄 @ahpook is way ahead of me.

@ahpook
Copy link
Contributor Author

ahpook commented Mar 20, 2024

I'm just getting things set up 👍 but yeah, my thought was that the board should live in github-ospo, along with any issues that are "meta" questions like the ones about unifying config files, requests for new actions etc. But issues related to a specific action should clearly stay in that action's repo.

@jmeridth
Copy link
Member

jmeridth commented Mar 22, 2024

@ahpook What verbiage would you want in the README's for each project so they point back to github.com/github/github-ospo?

Something like:

## Issues and PRs

All feedback regarding our GitHub Actions, as a whole, should be communicated through
[issues on our github-ospo repository](https://github.com/github/github-ospo/issues).

Issues and Pull Requests specific to this GitHub Action should be filed on this repository.

I ask so that I can include it in future PRs to each GitHub Action.

@lelia
Copy link

lelia commented Apr 5, 2024

@jmeridth From my POV that phrasing seems fine. My only note would be that perhaps it's worth adding an Issue Template in support of this type of feedback on github-ospo.

jmeridth added a commit to github/stale-repos that referenced this issue Apr 10, 2024
- [x] bug report
- [x] feature request
- [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)

Signed-off-by: jmeridth <[email protected]>
jmeridth added a commit to github/cleanowners that referenced this issue Apr 10, 2024
- [x] Issue Templates
  - [x] bug report
  - [x] feature request
  - [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)

Signed-off-by: jmeridth <[email protected]>
jmeridth added a commit to github/contributors that referenced this issue Apr 10, 2024
Closes #87

- [x] Issue Templates
  - [x] bug report
  - [x] feature request
  - [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)

Signed-off-by: jmeridth <[email protected]>
jmeridth added a commit to github/evergreen that referenced this issue Apr 10, 2024
Closes #89

- [x] Issue Templates
  - [x] bug report
  - [x] feature request
  - [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)
- [x] update .env-example to include github app installation auth examples env vars
- [x] clean up dependbot.yml

Signed-off-by: jmeridth <[email protected]>
jmeridth added a commit to github/issue-metrics that referenced this issue Apr 10, 2024
Closes #231

- [x] Issue Templates
  - [x] bug report
  - [x] feature request
  - [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)

Signed-off-by: jmeridth <[email protected]>
jmeridth added a commit to github/automatic-contrib-prs that referenced this issue Apr 10, 2024
Closes #51

- [x] Issue Templates
  - [x] bug report
  - [x] feature request
  - [x] config linking to discussions and github-ospo issues for overall issue filing
- [x] Update README linking to github-ospo repo issues for OSPO GitHub Actions issues as a whole (github/github-ospo#75)

Signed-off-by: jmeridth <[email protected]>
@jmeridth
Copy link
Member

@ahpook I believe this one is complete. All GitHub Actions READMEs have been updated to point back to this repository for overall issues.

@jmeridth jmeridth moved this from In progress to In review in GitHub OSPO OSS Board Apr 11, 2024
@ahpook
Copy link
Contributor Author

ahpook commented Apr 11, 2024

LGTM! Thanks JM

@ahpook ahpook closed this as completed Apr 11, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in GitHub OSPO OSS Board Apr 11, 2024
@Kya123iu

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ospo-actions Issues relating to the OSPO Actions
Projects
Status: Done
Development

No branches or pull requests

5 participants
@jmeridth @ahpook @lelia @Kya123iu and others