I even have the following use case:
Let’s say I have 2 repositories A and B. A is a software package deal and B is an additional tutorial containing some now not so not unusual use cases of that software bundle, both owned by means of me and public.
I even have Travis-CI currently running on A but now not B. Is it feasible to use Github Action to trigger Travis-CI in B (some thing like this, new dedicate in A will cause a sending of message “commit” in B so Travis will run in B everytime I actually have new commit project in A). So I can simply placed some vital checks in A travis-ci but additionally make sure the academic run pleasant in B.
I am looking to use GitHub template repositories to assist scaffold a challenge for new users, however it would be exquisite that placeholders in filenames and report contents might be vehicle changed when a new repository crafted from a template repo.
For example update js/ projectname .Controller.Js to be js/MyNewRepo.Controller.Js along with checking every files contents for the identical placeholder too.
Current mind for a workaround
This is my modern mind to the problem and the way I can also tackle it, happy for suggestions and or remarks
Build a new GitHub NodeJS action to help discover and update this in filenames and document contents
Have the template comprise a workflow YML file - as a way to auto run the find & replace
Use exec from @actions/exec npm bundle to run local Git instructions to devote & push the change again to the repo https://github.com/warrenbuckley/I-am-a-template/runs/214346350
From some extremely good hard paintings & initial checks it appears I can not push the changes again to the repo. Here is the output from the logs of the GitHub Action being run