search

near / near-workspaces-js

Write tests once, run them both on NEAR TestNet and a controlled NEAR Sandbox local environment
https://near.github.io/near-workspaces-js/
GNU General Public License v3.0
42 stars 21 forks source link

chore: update naj #102

Closed willemneal closed 2 years ago

willemneal commented 2 years ago

@volovyk-s @austinabell @ChaoticTempest

Is there any way to allow my account to trigger CI?

volovyks commented 2 years ago

@willemneal I guess the only way to do that is to turn it on for all developers. I don't have access to the settings in this repo. Sometimes I want to see CI status for external contributions too (in all repos) so I'm not against that. @MaximusHaximus do you have access? Are there any security concerns? I think that if the project is using GitHub actions, it should be fine, since it's free and runs on GitHub infrastracture.

willemneal commented 2 years ago

@volovyk-s Did it pass CI?

volovyks commented 2 years ago

I was not able to start the CI in this PR. So I tested it locally. Also, now you can see the status in the main branch. All good.

ChaoticTempest commented 2 years ago

I think it's just that github-actions is only listening on a push. Think we can change it to PRs as well and that will allow us to trigger CI for external people