-
Notifications
You must be signed in to change notification settings - Fork 1
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
Revisit checks #516
Comments
The checks used in Note: there is a discussion going on in parallel around standardizing our checks across the PACTA tech team. I would recommend closing this issue in favour of an issue/ discussion in that repo :-) |
@jdhoffa which issue exactly that is? I'm happy to move it there if it covers what I wanted to discuss here. Basically many times I had checks breaking for no reason and my intuition is that partly it is due to the fact that there are so many. Not sure if it is necessary to have so many checks for each PR. Maybe only for some when we make a release? |
Well it is not an issue, but the repository itself, where we plan to discuss what workflows to use for all repositories. Eventually, we will try to base all of our repositories workflows off of this central place so that we don't have a bunch of different versions of the same thing |
I just made a new issue covering it here: RMI-PACTA/actions#12 |
We will discuss it as well on February 1st I believe. I think @AlexAxthelm is going to send an invite. |
Closing this issue as the number and breadth of checks will be decided for all our repos when we solve this issue: RMI-PACTA/actions#12. |
Right now there seem to be a lot of checks on different OSes which might be an overkill
The text was updated successfully, but these errors were encountered: