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

DP-58: Fix internal HTTP links #6313

Merged
merged 2 commits into from
Jul 5, 2023
Merged

DP-58: Fix internal HTTP links #6313

merged 2 commits into from
Jul 5, 2023

Conversation

Bonrob2
Copy link
Contributor

@Bonrob2 Bonrob2 commented Jul 4, 2023

All Contributors

Contribution Checklist

  • Please make an issue in the OpenNMS issue tracker if there isn't one already.
    Once there is an issue, please:
    1. update the title of this PR to be in the format: ${JIRA-ISSUE-NUMBER}: subject of pull request
    2. update the Jira link at the bottom of this comment to refer to the real issue number
    3. prefix your commit messages with the issue number, if possible
    4. once you've created this PR, please link to it in a comment in the Jira issue
      Don't worry if this sounds like a lot, we can help you get things set up properly.
  • If this code is likely to affect the UI, did you name your branch with -smoke in it to trigger smoke tests?
  • If this is a new or updated feature, is there documentation for the new behavior?
  • If this is new code, are there unit and/or integration tests?
  • If this PR targets a foundation-* branch, does it try to avoid changing files in $OPENNMS_HOME/etc/?

What's Next?

A PR should be assigned at least 2 reviewers. If you know that someone would be a good person to review your code, feel free to add them.

If you need help making additions or changes to the documentation related to your changes, please let us know.

In any case, if anything is unclear or you want help getting your PR ready for merge, please don't hesitate to say something in the comments here,
or in the #opennms-development chat channel.

Once reviewer(s) accept the PR and the branch passes continuous integration, the PR is eligible for merge.

At that time, if you have commit access (are an OpenNMS Group employee or a member of the OGP) you are welcome to merge the PR when you're ready.
Otherwise, a reviewer can merge it for you.

Thanks for taking time to contribute!

External References

Updated internal links that pointed to HTTP.
DP-63: Add meta descriptions to each page in the deployment guide - began to add descriptions for better SEO.
DP-58: Fix internal HTTP links - updated internal HTTP links that should have been HTTPS.
DP-57: Add meta descriptions to each page in the deployment guide - added meta descriptions for each page in the deployment guide for better SEO. Did not add meta tag for pages that do not have H1, as these will be excluded in a future Jira.
@mmahacek
Copy link
Contributor

mmahacek commented Jul 4, 2023

Can you double check the target branch?

@Bonrob2 Bonrob2 changed the base branch from foundation-2022 to foundation-2023 July 4, 2023 15:24
@Bonrob2
Copy link
Contributor Author

Bonrob2 commented Jul 4, 2023

Can you double check the target branch?

Thanks!

@Bonrob2 Bonrob2 merged commit cfb44f5 into foundation-2023 Jul 5, 2023
4 checks passed
@Bonrob2 Bonrob2 deleted the jira/DP-58 branch July 5, 2023 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants