Add sync-template.yml workflow that synchronizes the repo with ubiquity/ts-template every month

[zyrafal]

Details: ubiquity/ts-template#54

[Keyrxng]

@zyrafal Thanks for the PR!

Could you please take a read through Conventional Commits as this is a standard we use across the org and CI will fail if these standards are not followed.

Please amend your commit title to something like feat: ... or chore: ..., thank you.

[ubiquity-os-deployer]

4021936

2413abc

[github-actions]

Preview Deployment
402193697dadfc60a2ffa13d3b002161a2680106
2413abc8c4c5aa7bd09ac468be33c069355ddcb9

[0x4007]

@zyrafal Thanks for the PR!

Could you please take a read through Conventional Commits as this is a standard we use across the org and CI will fail if these standards are not followed.

Please amend your commit title to something like feat: ... or chore: ..., thank you.

This contributor had to update like 10 repositories so we'll let it slide

[Keyrxng]

@zyrafal Thanks for the PR!
Could you please take a read through Conventional Commits as this is a standard we use across the org and CI will fail if these standards are not followed.
Please amend your commit title to something like feat: ... or chore: ..., thank you.

This contributor had to update like 10 repositories so we'll let it slide

I wasn't aware I thought it was their first PR

[Keyrxng]

https://github.com/ubq-testing/pay.ubq.fi/pull/3/files

This knocks out a lot of our stuff. build, css, tests, html...

Ideally the only stuff we want to sync is the config files, nothing else

I don't want to merge this until a task has been resolved that accurately ignores everything that we do not want synced.

The workflow appears to process IGNORE_FILES by name, so we'll have to manually specify all of the ignored files, and it also means relative url for each too which is going to be verbose.

Doesn't this introduce the problem where now every x months we need to manually review the ignored files?

[Keyrxng]

requesting changes so automated-merging won't do anything but I think it might not do anything anyway because CI has failed but just to be safe.

[0x4007]

https://github.com/ubq-testing/pay.ubq.fi/pull/3/files

This knocks out a lot of our stuff. build, css, tests, html...

Ideally the only stuff we want to sync is the config files, nothing else

I don't want to merge this until a task has been resolved that accurately ignores everything that we do not want synced.

The workflow appears to process IGNORE_FILES by name, so we'll have to manually specify all of the ignored files, and it also means relative url for each too which is going to be verbose.

Doesn't this introduce the problem where now every x months we need to manually review the ignored files?

Reviewing this now. Since this opens a pull request, I believe we only need to fix that pull once. Then it won't attempt to make the same changes again. Not 100% when it comes to git add .

@Keyrxng @whilefoo

[0x4007]

I think lets try and see what happens. The worst it does is open a pull after all. I really hope that next month wont be a mess with bad pulls!