automated action on update-profiles-csv.yml failing due to main branch protection

[timmwille]

 run extract.py
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Fix in the actions related to:
https://github.com/ASKnetCommunity/LEAD/blob/main/.github/workflows/update-profiles-csv.yml

[timmwille]

https://github.com/ASKnetCommunity/LEAD/actions/runs/4298100014

[timmwille]

@dutkulang @chardso we've got technicians work to do maybe @MartinSchott can help ;)

[chardso]

Great 👍

[timmwille]

not fixed yet

[timmwille]

Ok looks like the main problem is caused by the main branch protection → probably the solution is to trigger the action in another branch? or manually only and then do the merge in main? @MartinSchott @hoijui I'm not sure what is the best solution in this case?

[hoijui]

This is only a warning, which you can ignore for now:

Node.js 12 actions are deprecated

This is the real issue (as you already found out):

error: failed to push some refs to 'https://github.com/ASKnetCommunity/LEAD'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

... ouh boy, what did the children do when I left town for a night and day?!

Whenever you commit to main, you run a script that generates a file, and commits and pushes it to main ...

-> bad idea!
don't do that!

It is a generated file, so should not be in the repo. put it on your pages instead, and fetch it from there if needed, or generate it on the fly.