You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For this project, it seems that continuous integration is overkill. I am inclined to removing it. I feel like crying every time I checkpoint a part of my development and this runs CI, when I know perfectly well now is not the time to check for a complete re-compilation of the whole project.
At the very least, we should not run CI on theories when the only changes happened in the documents/ directory. I have a vague memory that we already discussed this, probably on zulip, but I am unable to find a trace of this conversation.
The text was updated successfully, but these errors were encountered:
I remember you talking about it after the Coq workshop.
Since the CI action is generated by a coq-community tool (https://github.com/coq-community/templates),
wouldn't it be worth asking the community?
CI wizards may have an easy solution that can benefit many.
Great! So it is a matter to edit the file docker-action.yml in .github/workflows?
I suspect that this will be required everytime the files are generated but this is not that often.
For this project, it seems that continuous integration is overkill. I am inclined to removing it. I feel like crying every time I checkpoint a part of my development and this runs CI, when I know perfectly well now is not the time to check for a complete re-compilation of the whole project.
At the very least, we should not run CI on theories when the only changes happened in the documents/ directory. I have a vague memory that we already discussed this, probably on zulip, but I am unable to find a trace of this conversation.
The text was updated successfully, but these errors were encountered: