I think it's definitely fine in the context of CI trial and error. I usually increment a counter on each commit. (Trying to get that HIGHSCORE)
That said, I clean it up using rebase and fixup so it makes sense chronologically when submitting a PR where context is important.
Glad to see that this is not so uncommon in CI. Recently added gitlabci to our projects and last whole week of commits looks like this:
Fix it. fix it again Not yet fixed Maybe now Nope This is it Yet another fix Finally You wished For godsake, please fix it
π
Dat high score tho βοΈ
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it's definitely fine in the context of CI trial and error. I usually increment a counter on each commit. (Trying to get that HIGHSCORE)
That said, I clean it up using rebase and fixup so it makes sense chronologically when submitting a PR where context is important.
Glad to see that this is not so uncommon in CI. Recently added gitlabci to our projects and last whole week of commits looks like this:
Fix it.
fix it again
Not yet fixed
Maybe now
Nope
This is it
Yet another fix
Finally
You wished
For godsake, please fix it
π
Dat high score tho βοΈ