fix comparison used to determine change in invalidations

[KristofferC]

#4 made the comparison go from a number comparison to a string comparison effectively breaking the workflow.

Fixes #16, #8

[KristofferC]

Is it really intended to install this workflow by copy pasting the check into every repo that uses it. A bug in that code (which is the case here) means that every single repo has to update their workflow. Shouldn't this be versioned somehow?

Anyway, there should probably be some mass action that opens PR to fix all the places where this workflow got added.

[KristofferC]

It might be possible to fix the existing actions by being sufficiently clever in updating how these values are stored:

julia-invalidations/action.yml

Lines 10 to 16 in 5d23709

	outputs:
	total:
	description: "Total number of invalidations"
	value: ${{ steps.invs.outputs.total }}
	deps:
	description: "Number of invalidations caused by deps"
	value: ${{ steps.invs.outputs.deps }}

so that if a < b then string(a) < string(b) (maybe via zero padding)

[ranocha]

Would changing

julia-invalidations/action.yml

Lines 61 to 62 in 5d23709

	println(io, "total=$(inv_total)")
	println(io, "deps=$(inv_deps)")

to something like

           println(io, @sprintf("total=%09d", inv_total)")
           println(io, @sprintf("deps=%09d", inv_deps)")

do this trick?

[KristofferC]

Maybe, I'm not sure exactly how github treats these things so I think it just has to be tested in practice.

[IanButterworth]

Has that been tried? It'd be good to get this in given maintenance attention on the action right now.