* Scaffold files for migration
* Move user-agent into unit suite
* Nothing to move from browser suite
* Migrate tests to translations/content
* Migrate existing translation test to meta
* No graphql tests to migrate
* Migrate lint-translation-reporter
* Migrate lint-translation-reporter
* Remove languages-schema, unused
* Restore languages-schema
* Restore languages-schema
* Migrate rendering
* Migrate routing
* Migrate most of unit
* Remove dead files, comment out tests that aren't expected to work yet
* Migrate from get-redirect
* Migrate page and pages
* Migrate linting code
* Fix lint issues
* Found a few more
* Run prettier
* Move crowdin-config test and helper
* Update crowdin-config.js
* Remove translation linting, crowdin config lint, reduce file count
* Remove test that's been skipped for a year
* Restore linting with note to remove later
* Update lint-translation-reporter.js
* Clean up rendering suite
* Update rendering.js
* Remove excessive describe blocks
* Redirect tests
* Clean up unit
* Remove test that's never called
* Don't compare early access
* Rename test suites
* Update "content" tests
* Update files.js
* Update search.js
* Update files.js
* Update files.js
* Move use session to its own hook file
* Trying useSWR
* Try one hour html cache
* blah blah lint
* Update to include loading state
* Update components/hooks/useSession.ts
Co-authored-by: Peter Bengtsson <peterbe@github.com>
Co-authored-by: Peter Bengtsson <peterbe@github.com>
* Remove theme from HTML
* update for linting error
* Fix for overriding default color modes
Co-authored-by: Grace Park <lugraciecy@gmail.com>
Co-authored-by: Grace Park <gracepark@github.com>
* Let be the caller, so events doesnt 403 on the first call
* Declare function
* Call all s so that the lang banner shows up consistently
* Update get-session.ts
* Recommend an `Accept` header for REST API requests which doesn't mention V3
In the documentation for every REST API, in the "Headers"
section, we say for the `Accept` header that:
> Setting to `application/vnd.github.v3+json` is recommended.
Putting the V3 bit in doesn't actually do anything - in fact,
a high proportion of API consumers don't do it - and this
recommendation is going to be confusing once we launch our
new API versioning. This recommends that people use
`application/vnd.gitrhub+json` instead.
We could just recommend `application/json` - I'd be in favour
of that! - but I'm trying to make this change as small as
possible.
* Update cURL and GitHub CLI code examples to use an `Accept` header without V3
Co-authored-by: Sarah Edwards <skedwards88@github.com>
* Working on tool picker
* Start on react version of tool picker
* Update ToolPicker.tsx
* Update tool-switcher.html
* Get it working
* Update browser.js
* Update browser.js
* Update ToolPicker.tsx
* adding switcher to creating a codespace guide
* adding additional switcher for vscode and updating codespaces name
* using webui in codespaces coontext
* updating internal documentation
* remove default tool
Co-authored-by: hubwriter <hubwriter@github.com>
* update article content to markdown ui component
* decouple lunr indexing from class name
* remove summary outline none rule, apply utility class instead
* improve typing
* scope more styles down to markdown-body/extended-markdown
* move all markdown-body style overrides to MarkdownContent component
* fix class targeting within css module
* clean up MarkdownContent header style
* rename data-lunr to data-search
* fix: inline code color issue
* fix: update article markdown to work with MarkdownContent
