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

Convert all referenced URLs with HTTP protocol to HTTPS #476

Conversation

sadielbartholomew
Copy link
Member

@sadielbartholomew sadielbartholomew commented Nov 10, 2023

See issue #463 for discussion of these changes.

Release checklist

  • Authors updated in cf-conventions.adoc?
  • Next version in cf-conventions.adoc up to date? Versioning inspired by SemVer.
  • history.adoc up to date?
  • Conformance document up-to-date?

For maintainers

After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then, main always is a draft for the next version.

The change was achieved using the shell command:
find . -type f -name "*.adoc" | xargs sed -i 's~http://~https://~g'
to cover all AsciiDoc files.
The change was achieved using the shell command:
find . -type f | xargs sed -i 's~http://~https://~g'
under the '.github' directory.
The change was achieved using the shell command:
find . -type f -name "*.md" | xargs sed -i 's~http://~https://~g'
to cover all Markdown files.
@sadielbartholomew sadielbartholomew added the defect Conventions text meaning not as intended, misleading, unclear, has typos, format or language errors label Nov 10, 2023
@sadielbartholomew sadielbartholomew self-assigned this Nov 10, 2023
@sadielbartholomew
Copy link
Member Author

RE the first checklist item, my name is set to be added to the 'additional authors' listing in cf-conventions.adoc through #469 (also very likely to be merged before this PR), so that is covered.

@sadielbartholomew
Copy link
Member Author

sadielbartholomew commented Nov 10, 2023

I've made the conversion and raised this PR today since time is short before the deadline for getting work in for CF 1.11, but I am yet to double check that all of the new links still work with the HTTPS instead of the HTTP protocol, as Dave Allured has suggested on the linked Issue.

I will check each link on Monday and confirm when I have done this (hopefully our link checking workflows can help, but I can always do it manually since there aren't too many to work through with a good coffee...).

Copy link
Member Author

@sadielbartholomew sadielbartholomew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A self review where I have gone through and checked that all links updated from HTTP to HTTPS still work, as promised last Friday. I have found that all do with the exceptions of (see in-line comments for locations, etc.):

Given the former, I will update this PR to not set HTTPS for those GeoTiff pages and comment as to why this is an exception to our preference for HTTPS.

ch01.adoc Outdated Show resolved Hide resolved
history.adoc Outdated Show resolved Hide resolved
appf.adoc Outdated Show resolved Hide resolved
history.adoc Outdated Show resolved Hide resolved
@sadielbartholomew
Copy link
Member Author

@larsbarring thanks for looking at this. The PR is now ready for re-review.

@sadielbartholomew
Copy link
Member Author

Approval to merge given expressed by @larsbarring in #463 (comment) and @JonathanGregory in #463 (comment), so I will now go ahead. Thanks everyone.

@sadielbartholomew sadielbartholomew merged commit b83f0d3 into cf-convention:main Nov 16, 2023
4 checks passed
@sadielbartholomew sadielbartholomew deleted the batch-update-http-protocol branch November 16, 2023 11:44
@davidhassell davidhassell added this to the 1.11 milestone Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Conventions text meaning not as intended, misleading, unclear, has typos, format or language errors
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants