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

CI recommendations #14

Open
frewsxcv opened this issue Sep 2, 2020 · 3 comments
Open

CI recommendations #14

frewsxcv opened this issue Sep 2, 2020 · 3 comments

Comments

@frewsxcv
Copy link
Member

frewsxcv commented Sep 2, 2020

Prefer GitHub Actions over Travis?

@michaelkirk
Copy link
Member

I don't want to be overly prescriptive, especially about any details that are likely to change, but a certain amount of management uniformity could ease the maintenance burden, especially as the number of repos we have grows.

How about:

  1. some level of CI
  2. bors integration which triggers CI and merges upon success

Anything to add? Anything to take away?

@urschrei
Copy link
Member

urschrei commented Mar 9, 2022

I think those are the minimum sensible requirements. I'd be comfortable with preferring (not prescribing) GitHub Actions as of 2022 with the understanding that this could change (could revisit once a year to update to "as of 2023" if need be). WDYT?

@michaelkirk
Copy link
Member

Yes, good idea. I'm happy to recommend specifically using github actions for now.

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

No branches or pull requests

3 participants