profile
viewpoint
Jessica Parsons verythorough @netlify SF Bay Area

issue commentnetlify/cli

Sync git remote parsing logic

@zachhardesty7 It turns out we have an internal feature request filed for that very thing! I've added a link to your comment for tracking.

DavidWells

comment created time in 6 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 8077183d6b9210afd3ca5320f4d0f50ab4f63c65

Another

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha b6397f5732c30d1ac0f8d52ea2097b6a3bfa7a3f

Quick change

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 4c90258f7034ec7142c767ac91c7eaa5455183bc

Simplify

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 404a4f18b8ad1d6444746ef19563e449acd54356

Update netlify.toml

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 91f19fd497c54f121e56da60cdabe4b0da4321a6

Update package.json

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 18f433597b1abf33c8433d86fbcf2833d1086a45

Delete hello_async.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 4da77db8e04021d9b18fd1d8a9e6de9e3ead8f92

Delete hello.js

view details

push time in 7 days

create barnchverythorough/netlify-functions-example

branch : test

created branch time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha ffded1cd3dd6479762bded3bd774fe6e82875bb5

Create hello.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 041c268362992d5ebfc269634c2164f84a43d2fe

Update netlify.toml

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 811eb50246932e77d2b8164ecd3462c5f7f498c6

Update hello.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 8424748c096a926e8c782777e3fab82e5d13217d

Update hello_env.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 72cfbcb3ab9dd0457b2f7a3cd6d2dfbbda16d59e

Update hello_env.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 2f4e36ba5e265ad1ad079ad1f77134d63cc5bfb5

Update netlify.toml

view details

push time in 7 days

push eventverythorough/functions

Jessica Parsons

commit sha d6fcaa4f2df949f1726eae15cf6ddcb83c7747f8

Update netlify.toml

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 0a0d79427c495360a21ed08ab50f357aad972092

Update hello_env.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha fa0c13459872b61e3a8a0e91b8d36c1ced700901

Update hello.js

view details

push time in 7 days

fork verythorough/functions

Playground repo for Netlify’s Lambda Functions

https://functions-playground.netlify.com

fork in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha f88bc370ee6107ce8e4e833c1a8cdcb3a8fa0098

Update hello.js

view details

push time in 7 days

push eventverythorough/netlify-functions-example

Jessica Parsons

commit sha 2d2866dde2467f4f190753c2447c2c0daf07582e

Update hello.js

view details

push time in 7 days

create barnchverythorough/netlify-functions-example

branch : master

created branch time in 7 days

created repositoryverythorough/netlify-functions-example

created time in 7 days

issue commentnetlify/cli

Sync git remote parsing logic

Ah, I see what you mean now. However, since that UI field is directly connected to the "automatic" setup for continuous deployment, I think that would actually be a much bigger change than fixing the bug in this issue.

In the end, maintaining two different commands that do essentially the same thing doesn't really make sense. I suspect that the best path forward is to make sure sites:create includes all of the functionality of init and then gradually deprecate init.

DavidWells

comment created time in 8 days

issue commentnetlify/cli

Sync git remote parsing logic

@zachhardesty7 or @Thms-Brnrd can you explain what you mean by "a way to modify the repo link via UI"?

DavidWells

comment created time in 19 days

push eventverythorough/mono-repo-example

Jessica Parsons

commit sha 8f5124c5c776470ccf64e046400193e4be5e7ee5

Update index.html

view details

push time in a month

create barnchverythorough/mono-repo-example

branch : new-test

created branch time in a month

delete branch verythorough/mono-repo-example

delete branch : testing

delete time in a month

push eventverythorough/mono-repo-example

Jessica Parsons

commit sha ca939ce92e28ed04c4f70b7dfc055d0c2e9583c0

Update index.html

view details

push time in a month

create barnchverythorough/mono-repo-example

branch : testing

created branch time in a month

delete branch verythorough/verythorough.github.io

delete branch : dependabot/bundler/nokogiri-1.10.5

delete time in a month

push eventverythorough/verythorough.github.io

dependabot[bot]

commit sha bf65f7620e7fa43fa0f027f1cf10aea7d95ba5f2

Bump nokogiri from 1.8.4 to 1.10.5 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.8.4 to 1.10.5. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.8.4...v1.10.5) Signed-off-by: dependabot[bot] <support@github.com>

view details

Jessica Parsons

commit sha 2847426c25087fd93f0efa726e10d2d6df0fb76c

Bump nokogiri from 1.8.4 to 1.10.5 (#13) Bump nokogiri from 1.8.4 to 1.10.5

view details

push time in a month

PR merged verythorough/verythorough.github.io

Bump nokogiri from 1.8.4 to 1.10.5 dependencies

Bumps nokogiri from 1.8.4 to 1.10.5. <details> <summary>Release notes</summary>

Sourced from nokogiri's releases.

1.10.5 / 2019-10-31

Dependencies

  • [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
  • [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34

1.10.4 / 2019-08-11

Security

Address CVE-2019-5477 (#1915)

A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's Kernel.open method. Processes are vulnerable only if the undocumented method Nokogiri::CSS::Tokenizer#load_file is being passed untrusted user input.

This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.

This CVE's public notice is sparklemotion/nokogiri#1915

1.10.3 / 2019-04-22

Security Notes

[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.

1.10.2 / 2019-03-24

Security

  • [MRI] Remove support from vendored libxml2 for future script macros. #1871
  • [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877

Bug fixes

  • [JRuby] Fix node ownership in duplicated documents. #1060
  • [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @​adjam!)

1.10.1 / 2019-01-13

Features

</tr></table> ... (truncated) </details> <details> <summary>Changelog</summary>

Sourced from nokogiri's changelog.

1.10.5 / 2019-10-31

Dependencies

  • [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
  • [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34

1.10.4 / 2019-08-11

Security

Address CVE-2019-5477 (#1915)

A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's Kernel.open method. Processes are vulnerable only if the undocumented method Nokogiri::CSS::Tokenizer#load_file is being passed untrusted user input.

This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.

This CVE's public notice is sparklemotion/nokogiri#1915

1.10.3 / 2019-04-22

Security Notes

[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.

1.10.2 / 2019-03-24

Security

  • [MRI] Remove support from vendored libxml2 for future script macros. #1871
  • [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877

Bug fixes

  • [JRuby] Fix node ownership in duplicated documents. #1060
  • [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @​adjam!)

1.10.1 / 2019-01-13

Features

</tr></table> ... (truncated) </details> <details> <summary>Commits</summary>

  • 1bc2ff9 version bump to v1.10.5
  • 383c1f8 update CHANGELOG
  • 43a1753 dependency: update libxslt to 1.1.34 final
  • 99d8a6b dependency: update libxml to 2.9.10 final
  • 2a86496 add suppressions for ruby 2.7
  • dca794a update CHANGELOG with correct release date for v1.10.4
  • 077e010 update rake-compiler commands to install bundler
  • beb832e version bump to v1.10.4
  • 5d30128 Merge branch '1915-css-tokenizer-load-file-vulnerability_v1.10.x' into v1.10.x
  • c86b5fc update CHANGELOG
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+5 -8

0 comment

1 changed file

dependabot[bot]

pr closed time in a month

issue commentnetlify/netlify-cms

Unmet peer dependencies

@jean I do like improving communication! I'm tagging @erquhart and @erezrokah to see your comment above, because they're the ones tasked with triaging issues and choosing which bots to add. :)

cedricdelpoux

comment created time in a month

issue commentnetlify/build-image

xenial image selects Ruby 2.3.6 by default

Closing because this seems to be working as expected. Feel free to re-open if there's something I missed!

abitrolly

comment created time in 2 months

issue commentnetlify/build-image

xenial image selects Ruby 2.3.6 by default

No, all previous deploy logs will still be there.

abitrolly

comment created time in 2 months

issue commentnetlify/build-image

xenial image selects Ruby 2.3.6 by default

I think the pinning will be reset if you re-connect your repo (under Settings > Build & deploy > Continuous deployment > Build settings). Of course, that just means everything will be re-pinned to the current defaults.

And to be clear, the pinning is there to avoid surprises. Without pinning, updates to the build image would causes change in your build, which is something we always want to avoid. You can read about how we handle dependencies here: https://docs.netlify.com/configure-builds/manage-dependencies/

abitrolly

comment created time in 2 months

issue commentnetlify/build-image

xenial image selects Ruby 2.3.6 by default

Ah, it looks like that site was created some time ago. Netlify pins the Ruby version on site creation so you don't have any unexpected changes when the build-image default updates. You can override the pinning by using either of the setting methods you linked above. :)

abitrolly

comment created time in 2 months

issue commentnetlify/build-image

Ruby version is not current with production build-image

No worries! It served as a good reminder to get #337 merged! 😁

motleydev

comment created time in 2 months

create barnchverythorough/vuepress-deploy

branch : master

created branch time in 2 months

created repositoryverythorough/vuepress-deploy

created time in 2 months

issue commentnetlify/build-image

Ruby version is not current with production build-image

If I understand correctly, you're talking about what's being fixed in this PR: https://github.com/netlify/build-image/pull/337. Is that right?

motleydev

comment created time in 2 months

PR opened vuejs/vuepress

fix($shared-utils): Add curly quotes to rSpecial

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

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

  • [x] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Docs
  • [ ] Build-related changes
  • [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

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

  • [x] Yes
  • [ ] No

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

This adds to the list of characters that convert to - in links. If there are any sites with existing headings that contain those characters, their links will change, potentially resulting in broken links. On the other hand, links that include those characters can behave unpredictably, so they wouldn't have been perfectly working links to begin with.

The PR fulfills these requirements:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

[I checked the link id's in the built html source.]

  • [ ] Chrome
  • [ ] Firefox
  • [ ] Safari
  • [ ] Edge
  • [ ] IE

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

  • [ ] A convincing reason for adding this feature
  • [ ] Related documents have been updated
  • [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information: I noticed that #1619 and #1855 also include changes to this file. Feel free to wrap this into one of those!

+1 -1

0 comment

1 changed file

pr created time in 2 months

push eventverythorough/vuepress

Jessica Parsons

commit sha 93652515baf58ae6065bb268cfc41ab06c1e2d47

fix($shared-utils): Add curly quotes to rSpecial

view details

push time in 2 months

fork verythorough/vuepress

📝 Minimalistic Vue-powered static site generator

https://vuepress.vuejs.org

fork in 2 months

push eventverythorough/verythorough.github.io

Jessica Parsons

commit sha db948b36356eb92b57a396f6cb220c33e9fdecb1

Update _redirects

view details

push time in 2 months

push eventverythorough/verythorough.github.io

Jessica Parsons

commit sha 3df09408b3f32cb2f7ac15c8ad5fb9c545bf01c6

Update _redirects

view details

push time in 2 months

create barnchverythorough/delete-one-click-hugo-cms

branch : master

created branch time in 2 months

created repositoryverythorough/delete-one-click-hugo-cms

created time in 2 months

issue commentnetlify/cli

Sync git remote parsing logic

Related: https://github.com/netlify/cli/issues/233

DavidWells

comment created time in 2 months

PR opened netlify/build-image

Add missing preinstalled Ruby versions

Updates the included software list for the Trusty branch to include all preinstalled Ruby versions, as installed in the Trusty Dockerfile and shown in deploy logs for sites using the Trusty image: included-versions

+3 -0

0 comment

1 changed file

pr created time in 3 months

push eventverythorough/build-image

Jessica Parsons

commit sha 4a60fd4b6f900477ecb70657c615faf9158fdf7e

Add missing preinstalled Ruby versions

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 2685013efcd62c7e2b287d825e746f2d0013237b

Delete .nvmrc

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha ed9368b670c05432bf6dbc5df5ecb4d0f590da9c

Change Node version to 10

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 9511bb6b075e08d600539d8bb6b36fcc85fb10ea

Remove yarn command

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha af0c9cd7b6c293d9953174d67544d85e9aac9199

Try yarn for build command

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha c3071a80d21bbc689c1f3bd45b0214998d62689c

Remove debug from build command

view details

push time in 3 months

create barnchverythorough/jekyll-basic-blog

branch : test

created branch time in 3 months

push eventverythorough/verythorough.github.io

Jessica Parsons

commit sha 82a4ace837c96a8417177a27d45d79b25728654f

Update .ruby-version

view details

push time in 3 months

fork verythorough/build-image

This is the build image used for running automated builds

fork in 3 months

push eventverythorough/verythorough.github.io

Jessica Parsons

commit sha 89270e1aca524c449c3699f8bfe262bf37060bfc

Update .ruby-version

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 531b1bcdf2ed6ea359bcd29d868acfbaafa483bc

Remove debug from build command

view details

push time in 3 months

push eventverythorough/eleventy-sustained

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 64a62ce3b5035b4c4ae75e72aef02d91b810886f

Update netlify.toml

view details

push time in 3 months

delete branch verythorough/eleventy-sustained

delete branch : dependabot/npm_and_yarn/lodash-4.17.14

delete time in 3 months

push eventverythorough/eleventy-sustained

dependabot[bot]

commit sha 2f7f84655af2827ed46ff94a91638b28345fc719

Bump lodash from 4.17.11 to 4.17.14 Bumps [lodash](https://github.com/lodash/lodash) from 4.17.11 to 4.17.14. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.11...4.17.14) Signed-off-by: dependabot[bot] <support@github.com>

view details

Jessica Parsons

commit sha 390dd425c4f8c9c3f302d4b64a720de4ee1cc15a

Bump lodash from 4.17.11 to 4.17.14 (#1) Bump lodash from 4.17.11 to 4.17.14

view details

push time in 3 months

PR merged verythorough/eleventy-sustained

Bump lodash from 4.17.11 to 4.17.14 dependencies

Bumps lodash from 4.17.11 to 4.17.14. <details> <summary>Commits</summary>

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

</details>

+33 -14

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 39b89410dc51242c253ded6609a073431b56057b

Update netlify.toml

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 42b19f4b07f07abc4996a417968bbe2e03124eee

Update netlify.toml

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 94f2516233f400cbb609609bb3ae611ea71ab49f

Update netlify.toml

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha b00dd66c05195d0c07511cf996aa3069b5651d2e

Update netlify.toml

view details

push time in 3 months

push eventverythorough/eleventy-sustained

Jessica Parsons

commit sha 00313ad29e1531ce148e0145fc2da6bdc17be34a

Update netlify.toml

view details

push time in 3 months

issue commentnetlify/open-api

Add code samples

@ramigs That sounds great! Until we figure out exactly which tech we'll use for the open-api docs long term, I think adding the examples to the readme of the netlify/js-client repo is a nice way to get stuff up quickly.

In terms of reporting possible issues, it's possible to report in either repo, since the issues can be moved if necessary. I also recommend asking questions like that in the Netlify Community forums. The Netlify support team is in there every day, and there are lots of community member who can help troubleshoot as well.

One quick tip in determining whether a problem is a bug in the API, the js-client, or your own code: if the thing you are trying to do can be done in the Netlify UI (like your build hooks example), the bug is probably not in the API itself, because the UI uses the API (check the Network tab calls 😉). If the thing can be done in the Netlify CLI (which uses the js-client), then it probably isn't the js-client (and you might check the CLI repo code to help troubleshoot your own js-client usage).

In the particular case of the build hooks, I haven't tried using the js-client createSiteBuildHook() method, but I can successfully make a POST to the build_hooks endpoint in Postman and have my title and branch set properly and display in the UI. I did have to send the payload as either form-data or x-www-form-urlencoded, though, so I suspect that you may not be passing your parameters to the function in the right format. I'll bet you could get some quick answers about that in the community forums.

ehmicky

comment created time in 3 months

issue commentnetlify/open-api

Tags are breaking the structure of the Go client

I don't suppose that would mean we could move away from go-swagger and upgrade to OpenAPI 3.0?

mraerino

comment created time in 3 months

issue commentnetlify/open-api

create process with netlify's dev team to add new attributes and calls <EOM>

Yeah, I suppose "process" over-sells it a bit. 😛

fool

comment created time in 3 months

issue commentnetlify/open-api

create process with netlify's dev team to add new attributes and calls <EOM>

Yes! As we keep moving towards more "docs-driven devlopment", we're hoping to have it be part of the API dev process to PR changes to the OpenAPI definition before working on changes.

(Of course, we'll also need some sort of process for finding and correcting existing gaps.)

fool

comment created time in 3 months

Pull request review commentnetlify/cli

Update API documentation URLs

 class AddonsListCommand extends Command {      const siteData = await api.getSite({ siteId }) -    // TODO update getAddons to https://open-api.netlify.com/#/default/getServices+    // TODO update getAddons to https://open-api.netlify.com/#/operation/getServices
    // TODO update getAddons to https://open-api.netlify.com/#operation/getServices
ehmicky

comment created time in 3 months

Pull request review commentnetlify/cli

Update API documentation URLs

 class AddonsDeleteCommand extends Command {     }     let addonResponse     try {-      // TODO update deleteAddon to https://open-api.netlify.com/#/default/deleteServiceInstance+      // TODO update deleteAddon to https://open-api.netlify.com/#/operation/deleteServiceInstance
      // TODO update deleteAddon to https://open-api.netlify.com/#operation/deleteServiceInstance
ehmicky

comment created time in 3 months

Pull request review commentnetlify/cli

Update API documentation URLs

 class AddonsCreateCommand extends Command { async function createSiteAddon({ addonName, settings, accessToken, siteData, error }, logger) {   let addonResponse   try {-    // TODO update to https://open-api.netlify.com/#/default/createServiceInstance+    // TODO update to https://open-api.netlify.com/#/operation/createServiceInstance
    // TODO update to https://open-api.netlify.com/#operation/createServiceInstance
ehmicky

comment created time in 3 months

Pull request review commentnetlify/cli

Update API documentation URLs

 async function update({ addonName, currentConfig, newConfig, settings, accessTok    let updateAddonResponse   try {-    // TODO update updateAddon to https://open-api.netlify.com/#/default/updateServiceInstance+    // TODO update updateAddon to https://open-api.netlify.com/#/operation/updateServiceInstance
    // TODO update updateAddon to https://open-api.netlify.com/#operation/updateServiceInstance
ehmicky

comment created time in 3 months

Pull request review commentnetlify/cli

Update API documentation URLs

 class AddonsConfigCommand extends Command {       return false     } -    // TODO update getAddonManifest to https://open-api.netlify.com/#/default/showServiceManifest+    // TODO update getAddonManifest to https://open-api.netlify.com/#/operation/showServiceManifest

It looks like these links don't work with the / after the #

    // TODO update getAddonManifest to https://open-api.netlify.com/#operation/showServiceManifest
ehmicky

comment created time in 3 months

push eventverythorough/bigurl

elstamey

commit sha a0f06ef62507716b8085eee8641610ce407577d2

corrected a typo Hi! I discovered that the word bookmarklet was misspelled

view details

Jessica Parsons

commit sha a6d15679553b833b7350bb94015423c4789987f3

Merge pull request #1 from elstamey/patch-1 corrected a typo

view details

push time in 3 months

PR merged verythorough/bigurl

corrected a typo

Hi! I discovered that the word bookmarklet was misspelled. I hope you are doing well!

+3 -3

1 comment

1 changed file

elstamey

pr closed time in 3 months

pull request commentverythorough/bigurl

corrected a typo

Oh, thanks! Do you actually use it? I do, and I'm always meaning to make improvements, but never get to it. Hope all is well with you, too!

elstamey

comment created time in 3 months

Pull request review commentnetlify/open-api

Add `description` field

 info:   version: 0.11.4   title: Netlify's API definition   termsOfService: https://www.netlify.com/legal/terms-of-use/+  description: >-+    Netlify is a hosting service for the programmable web. It understands your+    documents and provides an API to handle atomic deploys of websites, manage+    form submissions, inject JavaScript snippets, and much more. This is a+    REST-style API that uses JSON for serialization and OAuth 2 for+    authentication.+++    This document describes common usage in some detail. There is also an+    OpenAPI reference for the Netlify API that you can explore. Visit our

The "OpenAPI reference" mentioned here is this very page! I would reverse those two descriptions. In other words, explain that this site is a reference, and for more detailed instructions for common uses, visit netlify.com/docs/api.

ehmicky

comment created time in 3 months

Pull request review commentnetlify/open-api

Add `description` field

 info:   version: 0.11.4   title: Netlify's API definition   termsOfService: https://www.netlify.com/legal/terms-of-use/+  description: >-+    Netlify is a hosting service for the programmable web. It understands your+    documents and provides an API to handle atomic deploys of websites, manage+    form submissions, inject JavaScript snippets, and much more. This is a+    REST-style API that uses JSON for serialization and OAuth 2 for+    authentication.+++    This document describes common usage in some detail. There is also an+    OpenAPI reference for the Netlify API that you can explore. Visit our+    Community forum to join the conversation about understanding and using

I'd also add back the community link that's in that intro at netlify.com/docs/api.

ehmicky

comment created time in 3 months

create barnchverythorough/new_netlify_identity_example

branch : master

created branch time in 3 months

created repositoryverythorough/new_netlify_identity_example

created time in 3 months

push eventverythorough/docusaurus-base

Jessica Parsons

commit sha 4bd76ad100e00ed43d7b5d3c076a495a02e9f8ec

Create yarn.lock

view details

push time in 3 months

push eventverythorough/docusaurus-base

Jessica Parsons

commit sha 97ead93b2d5d7bd7d8f9ad77652086c306d85b92

Update netlify.toml

view details

push time in 3 months

create barnchverythorough/docusaurus-base

branch : master

created branch time in 3 months

created repositoryverythorough/docusaurus-base

created time in 3 months

pull request commentnetlify/open-api

Enhance documentation UI

Oof, bummer redirects won't work since those are all behind a hash. :(

ehmicky

comment created time in 3 months

push eventverythorough/mkdocs-base

Jessica Parsons

commit sha e32aa00b920397d29f92cdac997e18280b3e36b6

Update runtime.txt

view details

push time in 3 months

more