Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix note visibility on gpg 2.4+ usage #29647

Merged
merged 2 commits into from
Jun 13, 2024
Merged

Conversation

jmartens
Copy link
Contributor

The details section was encompassing the whole key creation section hiding an important note for gpg 2.4+ users

Changes

The details section was encompassing the whole key creation section hiding an important note for gpg 2.4+ users

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

jmartens and others added 2 commits June 13, 2024 10:35
The details section was encompassing the whole key creation section hiding an important note for  gpg 2.4+ users
@viceice viceice changed the title fix(docs): fix note visibility on gpg 2.4+ usage docs: fix note visibility on gpg 2.4+ usage Jun 13, 2024
@viceice viceice added this pull request to the merge queue Jun 13, 2024
Merged via the queue into renovatebot:main with commit d1aea9f Jun 13, 2024
37 checks passed
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.407.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@jmartens jmartens deleted the patch-1 branch June 13, 2024 17:44
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants