Closed JesseHufstetlerNortridge closed 6 months ago
@JesseHufstetlerNortridge , d/k why bot is re-posting about CLA. I haven't seen that behavior. If needed, I could create a fresh PR with all these commits, and Close Without Merging the present PR. A nice thing about using present PR is that the article will list you as contributor, i think.
I might delete some bot posts here ... they went away. I just have the multiple emails.
Learn Build status updates of commit bf93d24:
File | Status | Preview URL | Details |
---|---|---|---|
microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md | :white_check_mark:Succeeded | View |
For more details, please refer to the build report.
For any questions, please:
@JesseHufstetlerNortridge please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
- (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
- (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
@JesseHufstetlerNortridge - Can you "sign" the Contributor License Agreement, per emails from GitHub and per the above bot post?
If not, I think I'll need to create a fresh PR, and close-without-merging the present PR. This PR has been approved (by two teams).
I believe if you sign CLA so this PR can be merged, you will be listed as a contributor at top of article: "Overview and timelines for migrating to Manifest V3" https://learn.microsoft.com/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 I'll monitor this PR to check whether that's the case.
Learn Build status updates of commit b5d3dbb:
File | Status | Preview URL | Details |
---|---|---|---|
microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md | :white_check_mark:Succeeded | View |
For more details, please refer to the build report.
For any questions, please:
This PR 3041 is being replaced by PR #3076.
Updated PR https://github.com/MicrosoftDocs/edge-developer/pull/3076 to remove the date from the sentence. @JesseHufstetlerNortridge
Rendered article section for review:
v3 is coming June (not Jan) 2024, per: https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline [except that depends whether using enterprise policies, which is the scenario that the original paragraph specified - m.h.]
Update by m.h.:
AB#48777833