Maven deploy action should only be initiated from Mekom repository
Closed this issue · 1 comments
mseaton commented
Currently there is a Github Action to build, test, and publish new artifacts on any commit make to the master branch. However, this does not have any restriction on which fork this can come from. So, if I have the initializer module forked to my personal github, and I push a new commit to it (eg. my merging up from master), this will try to build and deploy from my fork to the Mekom Nexus repository (and will always fail due to lack of credentials).
The github action should have conditionals added to it which will not try to do a deploy outside of the Mekom fork.