Best way to keep commit history clean when iterating w github actions?

[ruby remnant]

Hi guys, i had a small issue recently but i notice its recurring especially in docker related stuff.

Yesterday, i had issues with networking and my dockerfile build on github actions.

For the dockerfile, i tried "changing the jar target directory", but to actually test this i have to push to github. So then i push that and it doesnt work, so like i remove it and change it again and push that and it aslo doesnt work. So then i do another etc. and i have like 7 or 8 commits.

Then with the networking, like i change the docker compose too and this for me is very iterative.

I get i can make another branch, but if its a public repo its a bit awkward just having this out in the open. I guess then i'd squash merge into main once fixed?

Just wondering what the best way might be / how you guys do it.

[brittle flame]

force push after cleaning your ugly actions

(or just make a branch and then squash merge delete)

[ruby remnant]

but don't i need to push for the action to run?

[ruby remnant]

Thats what i thought too, oke that makes sense

[brittle flame]

ye sure

but after that you force push to get rid of the commits lol

rewrite history

[ruby remnant]

ohhhhh

[ruby remnant]

so like

local master branch: last working

local iteration branch: has the ugly commits

Push to remote iteration branch

Once works on iteration branch, move the local iteration branch onto the local master one? And push the local master with one clean commit? And delete the remote one

or along these lines?

[brittle flame]

ye