-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test changing test data #41
base: master
Are you sure you want to change the base?
Conversation
as slash command and trigger run-all-tool-test only from issues
…test-data Topic/update test data
add resonse comment
d0ec4b1
to
a9809ef
Compare
a9809ef
to
9789f9d
Compare
/update-test-data |
Hmm.. Seems that the bot can't push to your branch: This might be solvable for the autoupdate mechanism, but I have no idea how to deal with this in general ... |
/update-test-data |
@simonbray just invidet you as collaborator to this project. lets see if you can start update of test data |
/update-test-data |
Still
|
/update-test-data |
Same |
Maybe its possible to trigger the workflow on your branch .. have to think about this |
@bernt-matthias is it possible that I grant the bot access to my fork? I know how to do this for github users, but no idea for actions. An alternative could be that if the bot cannot push to a branch, to make a pull request instead? Maybe also posting a comment requesting access. |
|
Don't know.
Good idea. I guess we can manage for the autoupdates to push directly. But in general a PR should be a good fallback. |
/update-test-data |
@bernt-matthias could you accept my collaboration invite? We didn't try this yet and to me it makes sense (your action is making a change to my fork). |
Done |
/update-test-data |
FOR CONTRIBUTOR: