Skip to content

Conversation

him2him2
Copy link
Contributor

URLs updated to use HTTPS protocol where appropriate to improve security and privacy.

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • [X ] Other, please describe:
    URLs updated to use HTTPS protocol where appropriate to improve security and privacy.

Does this PR introduce a breaking change? (check one)

  • Yes
  • [ X ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

URLs updated to use HTTPS protocol where appropriate to improve security and privacy.
Copy link
Member

@posva posva left a comment

Choose a reason for hiding this comment

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

Can you remove all the changes before Browser compatibility? Those are automatically generated anyway

URLs updated to use HTTPS protocol where appropriate to improve security and privacy.
Copy link
Member

@posva posva left a comment

Choose a reason for hiding this comment

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

Thanks!

@posva posva changed the title Update HTTP -> HTTPS chore: update HTTP -> HTTPS Oct 16, 2020
@posva posva merged commit b800e8e into vuejs:dev Oct 16, 2020
@him2him2
Copy link
Contributor Author

Hi Posva, As requested, I removed changes to auto generated part of page and recommitted the changes. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants