add Jorge as author

[JorgeG94]

No description provided.

[chrisb13]

Thanks @JorgeG94!

@atteggiani, quite a few failing checks here:

• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594467903?pr=43 (failed)
• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594467934?pr=43 (failed)
• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594491954?pr=43 (skipped)

Haven't seen these ones before so any ideas welcome! Given the edits are trivial I assume the errors are unrelated.

[atteggiani]

Thanks @JorgeG94!

@atteggiani, quite a few failing checks here:

• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594467903?pr=43 (failed)
• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594467934?pr=43 (failed)
• https://github.com/ACCESS-Community-Hub/decoding-om3/actions/runs/27598702244/job/81594491954?pr=43 (skipped)

Haven't seen these ones before so any ideas welcome! Given the edits are trivial I assume the errors are unrelated.

I've never seen this error. Very strange.
Not sure what's going wrong here though, because the same workflow runs fine in other repos...

I'm sorry but I don't have a better advice other than removing the link checker for the moment, until we find a more consistent and low-maintenance solution.

[chrisb13]

I've never seen this error. Very strange. Not sure what's going wrong here though, because the same workflow runs fine in other repos...

H'm that is weird because I think it has only appeared after our recent discussed update (that was supposed to help fix this stuff!).

Is there a way we can move past these two failing checks and at least recover the link checking? (I'm guessing this error will still persist)

I'm sorry but I don't have a better advice other than removing the link checker for the moment, until we find a more consistent and low-maintenance solution.

Can you please make this change/open an issue? I'm not sure how to remove it.

As such, I think leaving it in but broken is okay if you think a fix might be possible in the mid-term future.

[atteggiani]

Can you please make this change/open an issue? I'm not sure how to remove it.

As such, I think leaving it in but broken is okay if you think a fix might be possible in the mid-term future.

I disabled the workflow so it should not trigger anymore (it will still be in the repo).
Hopefully we'll have a better solution soon

[chrisb13]

Ok, it still seems to be in this PR but I assume you mean it won't come up in future ones?

I'll go ahead and merge this.