It says cryptographically unverified, when it in fact _is_ cryptographically verified.
I'd suggest Github changes this scenario to `partially verified` at the very least (as opposed to "WARNING! WARNING! UNVERIFIED!", but ideally I'd like to be allowed to set whatever author email I want in my git commits, without that impeding on the veracity of my GPG signatures.
My use-case is to not spread an email I care about more than I have to. Enough trawlers already - few if any care to parse GPG keys and extract (it seems).
9/10 times (in my personal experience) they just trawl github commit logs with a webscraping service instead.
Those who think that they must match (that the git commit/tag author email gives any security at all) have a nasty surprise-in-waiting.
* move workflow disable content to tool selector
* add cli tab to workflow articles
* seeing if this works
* add reusable
* update for each platform
* update with flags
* update with product switchers
* update with end tag
* add cli tab
* update with cli and desktop tabs
* add desktop and cli tabs
* remove tip
* get tests passing
* last small updates
* fix break
* remove break maybe
* update with download link reusable
* update with download resuable
* resolve feedback
* quotes around string
* flesh this out a bit more
* remove reusable
* update with more feedback
Co-authored-by: Meg Bird <megbird@github.com>
* bring over copilot content and assets from docs-early-access
* Remove broken link and update footnotes
* Fix broken link
* Add data set to `docs-internal` and revert footntoes
* add redirects from old early access paths
Co-authored-by: Ethan P <56270045+ethanpalm@users.noreply.github.com>
* add beta note and mention using high contrast theme
* update screenshots
* add feature preview note to step
* update settings menu item
* update language
* use full theme name
* Apply suggestions from code review
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* version text
* version screenshots too
* build
* move beta callout below
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
* Clarify squash and merge default commit message
Originally reported in https://github.com/github/coding/issues/1865, a customer was confused to find that merge commits don't count toward the total count of commits to determine this default squash merge commit message.
* Update content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
* Move category to top-level doc set
* Move doc set to the top and update short title
* Undo package-lock changes
* updated hardcoded refs in tests
* Update test
* Fix hardcoded link in test
Co-authored-by: Sarah Schneider <sarahs@github.com>
