403 error when proposing changes to docs via stackblitz

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Reproduce the flow from the project-structure/src/fonts.md page through StackBlitz, using the documented edit, Propose changes, and Fork & Commit changes steps. Inspect the browser console when the request fails with 403; done means a documentation change can be proposed and committed without that error.

Written by the indexing model from the issue text.

Description

Repro:

  1. From https://docs.nativescript.org/project-structure/src/fonts click on "Edit this page" (brings you to https://stackblitz.com/~/github.com/NativeScript/docs/edit/main/content/project-structure/src/fonts.md?initialPath=%2Fproject-structure%2Fsrc%2Ffonts)
  2. Edit doc. Ex: I'm trying to add this section (remove the leading \ on codeblock)
::: warning Note Material icons users
Material icons uses [Ligatures](https://developer.mozilla.org/en-US/docs/Glossary/Ligature) instead of char codes. 

\```xml
<Label class="mat-icon-filled" text="person" />
\```
:::
  1. Hit "Propose changes" button, then "Fork & Commit changes"
  2. View error in browser console:
Image
Dominant language
JavaScript
Stars
17
Forks
31
Avg merge
8h 51m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NativeScript/docs

All issues in NativeScript/docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.