Move cgmanifest.json

[barcharcraz]

Please note that acceptance of community PRs will be delayed while we are
bringing our test and CI systems online. For more information, see the
README.md.

Description

Move CGmanifest to a more appropriate location. Fixes #125.

mirror of internal PR https://devdiv.visualstudio.com/DevDiv/_git/msvc/pullrequest/204398?_a=overview

Checklist:

• I understand README.md.
• If this is a feature addition, that feature has been voted into the C++
  Working Draft.
• Identifiers in any product code changes are properly _Ugly as per
  https://eel.is/c++draft/lex.name#3.1 .
• Identifiers in test code changes are not _Ugly.
• Test code includes the correct headers as per the Standard, not just
  what happens to compile.
• The STL builds and test harnesses have passed (must be manually verified
  by an STL maintainer before CI is online, leave this unchecked for initial
  submission).
• This change introduces no known ABI breaks (adding members, renaming
  members, adding virtual functions, changing whether a type is an aggregate or
  trivially copyable, etc.). If unsure, leave this box unchecked and ask a
  maintainer for help.

[CaseyCarter]

Oh no, the singularity! AHHHHhhhhhhhhh...... (No change requested.)

[StephanTLavavej]

I capitalized your PR title, and edited the description to mention which GitHub issue this fixes. Looks good to me.

[CaseyCarter]

I capitalized your PR title, and edited the description to mention which GitHub issue this fixes. Looks good to me.

Be sure to edit these changes into the commit log, either when merging or now with a force-push*.

*Ideally, --force-with-lease, which is a bit safer if other folks may have pushed into the branch.

[StephanTLavavej]

I am still unclear as to what happens when we press "Squash and merge". Does this ever use the original commit? This is related to whether commits appear as "Verified" or not, and why not all of them in the history are.

[BillyONeal]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[sylveon]

@StephanTLavavej Squash and merge combines all commits of the PR into one, and adds that commit to the target branch. The resulting squashed commit is shown as verified because it is signed with GitHub's GPG key. PRs which are merged using the rebase or merge commit strategy aren't signed by GitHub. Rebase merges can't be verified because they edit the commits to replay them on top of the target branch and therefore break the signature, but merge commit merges will show verified on the original commits if the author signed them with their GPG key because it does not edit the commits.

[BillyONeal]

@sylveon It can't be just that because #114 was squashed but still doesn't show 'Verified'

[CaseyCarter]

@sylveon It can't be just that because #114 was squashed but still doesn't show 'Verified'

#114 squashed unverified commits: https://github.com/microsoft/STL/pull/114/commits, so it wouldn't be signed.

[BillyONeal]

#114 squashed unverified commits: https://github.com/microsoft/STL/pull/114/commits, so it wouldn't be signed.

#134 squashed unverified comments and shows up as "verified".

[sylveon]

Then I'm not sure what's happening here.

[BillyONeal]

That makes several of us :)