Fixed broken link to sops readme heading

[ginkogruen]

I noticed the link wasn't linking to the heading correctly so I fixed it.
Apparently it had changed again.

[dasJ]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The pull request can't be updated.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[ginkogruen]

It seems mergify-bot has some sort of hiccup (or permission error if I'm reading correctly). Could someone take a look at this?

[Mic92]

Looks like it doesn't work because you didn't allow maintainers to make changes to your feature branch.

[ginkogruen]

That's the checkmark below the participants on here right? It was checked the whole time. I going to try unchecking and rechecking that.

If there are any other options I need to check/uncheck I would be grateful for some pointers. To my knowledge I didn't change anything and kept things default.

[ginkogruen]

So I've accidentally synced my fork. I thought this might change some permission things about mergify but in hindsight I'm not too sure about that.

I still would like to get this merged. Is it still possible with the synced fork?
Also maybe the permissions did change after I unchecked and re-checked the box.

So If there aren't any other setting I need to check maybe mergify would work this time.
Otherwise I think it may be better If someone else who understands mergify and GitHub does the commit.

[Mic92]

The old link https://github.com/getsops/sops#using-sops-yaml-conf-to-select-kms-pgp-and-age-for-new-files works for me but not the new one: https://github.com/getsops/sops#using-sopsyaml-conf-to-select-kms-pgp-and-age-for-new-files

[ginkogruen]

Yes I can confirm the old link seems to be working again. I did some digging around and it seems that GitHub changed how they render .rst documents which caused some things (including the Table of Contents) to not render correctly.
I guess this changed some of the heading links too.

For reference:

• Archive.org of the improperly rendered .rst
• People reporting issues about improper rendering
• RST section title including ".*" and without blank line after adornment characters wrongly renders as inline markup jgm/pandoc#9805 - This may have fixed it