Closed thomasgilmore closed 2 years ago
Hi @thomasgilmore95!, thanks for the Pull Request
The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
โ๏ธ Deploy Preview for eslint ready!
๐จ Explore the source changes: b449ef5f51b39cdcfbf25b5e56629db48b66082e
๐ Inspect the deploy log: https://app.netlify.com/sites/eslint/deploys/6184ac7e9f17fb0007aa293a
๐ Browse the preview: https://deploy-preview-885--eslint.netlify.app/blog/2021/11/the-inception-of-eslint
Hi @thomasgilmore95!, thanks for the Pull Request
The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
@nzakas I'm not sure how to fix the commit message error. I've changed the PR Title and changed the commit message. I think I'm missing something.
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
@thomasgilmore95 we have started to use the conventional commits. https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
Hi @thomasgilmore95!, thanks for the Pull Request
The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.
Read more about contributing to ESLint here
no worries, I've fixed the title.
@aladdin-add thank you
I added the gist blog post to see it in deploy preview.
Looks like it's not working: https://deploy-preview-885--eslint.netlify.app/blog/2018/02/the-inception-of-eslint
The canonical URL isn't the original URL.
I tested the canonical url and it comes back href(unknown)
. I made a commit so you could see it as well.
Is there another way to access the page's front matter variables.
I donโt know Eleventy well enough to answer that. Iโd suggest checking the docs: https://www.11ty.dev/docs/data-frontmatter/
Thank you that link was helpful. The canonical link is being show know if original is present.
Please let me know if you want me to make any changes.
Thank you for letting me work on this.
Adding canonical links to blog posts. This pull request solves issue #568