Skip to content
This repository has been archived by the owner on Sep 13, 2023. It is now read-only.

CI: allow lint and short tests for everyone #695

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

omesser
Copy link
Contributor

@omesser omesser commented Jul 13, 2023

addresses: #330 (maybe partially, at least)
Allow basic checks and short ci tests without approval. need approvals for framework tests

@omesser omesser requested a review from a team as a code owner July 13, 2023 20:37
@omesser omesser temporarily deployed to external July 13, 2023 20:37 — with GitHub Actions Inactive
@omesser omesser marked this pull request as draft July 13, 2023 20:37
@omesser omesser temporarily deployed to external July 13, 2023 20:51 — with GitHub Actions Inactive
@omesser omesser temporarily deployed to external July 13, 2023 20:56 — with GitHub Actions Inactive
@omesser omesser added the 🏡 housekeeping Fighting technical debt and improving dev process label Jul 13, 2023
@omesser omesser changed the title CI edits - allow lint and short tests for everyone CI: allow lint and short tests for everyone Jul 13, 2023
@codecov
Copy link

codecov bot commented Jul 13, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (a726314) 82.71% compared to head (d6b91e3) 82.71%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #695   +/-   ##
=======================================
  Coverage   82.71%   82.71%           
=======================================
  Files         109      109           
  Lines        9943     9943           
=======================================
  Hits         8224     8224           
  Misses       1719     1719           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@omesser omesser temporarily deployed to external July 13, 2023 21:32 — with GitHub Actions Inactive
@omesser omesser temporarily deployed to external July 13, 2023 21:48 — with GitHub Actions Inactive
@omesser omesser closed this Jul 21, 2023
@omesser omesser reopened this Jul 21, 2023
@omesser omesser temporarily deployed to external July 21, 2023 07:59 — with GitHub Actions Inactive
@omesser omesser marked this pull request as ready for review July 21, 2023 15:29
@omesser omesser temporarily deployed to external July 21, 2023 15:30 — with GitHub Actions Inactive
@omesser omesser closed this Jul 21, 2023
@omesser omesser reopened this Jul 21, 2023
@omesser omesser temporarily deployed to external July 21, 2023 22:57 — with GitHub Actions Inactive
@omesser omesser temporarily deployed to external July 22, 2023 16:53 — with GitHub Actions Inactive
@omesser omesser closed this Aug 1, 2023
@omesser omesser reopened this Aug 1, 2023
@omesser omesser temporarily deployed to external August 1, 2023 11:09 — with GitHub Actions Inactive
Comment on lines +97 to +104
GITHUB_USERNAME: ${{ secrets.GH_USERNAME }}
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
GITHUB_MATRIX_OS: ${{ matrix.os }}
GITHUB_MATRIX_PYTHON: ${{ matrix.python }}
BITBUCKET_USERNAME: ${{ secrets.BITBUCKET_USERNAME }}
BITBUCKET_PASSWORD: ${{ secrets.BITBUCKET_PASSWORD }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC, initial idea was to allow external contributors to run tests that don't require using secrets #330 #318. But here you do exactly opposite, no?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to recall how we ended up with this authorize step, and IIRC, it was the case that CI/CD doesn't run for external contributors at all because GH doesn't allow them to use secrets we put to the repo. If that's true, we need to actually separate tests to two parts: one that requires secrets, and the other that doesn't.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should've moved this back to draft, my bad sorry. I moved attention elsewhere but I'll catch up with you again before coming back to this.

Copy link
Contributor

@aguschin aguschin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand this ^

@omesser omesser marked this pull request as draft August 23, 2023 13:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🏡 housekeeping Fighting technical debt and improving dev process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants