Repository navigation
Allow live Graph testing in any tenant, reaching only your own accounts - #21
Merged
Merged
Conversation
The pull request template, CONTRIBUTING.md, and RELEASING.md asked for live Microsoft Graph testing in a test tenant. What matters is that the test reaches nobody who didn't agree to it, and most contributors have no test tenant, so all three now ask for that instead: any tenant the tester is allowed to test in, with messages and files going only to accounts they control.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The pull request template,
CONTRIBUTING.md, andRELEASING.mdasked for live Microsoft Graph testing to happenin a test tenant. What matters is that a test reaches nobody who didn't agree to it, and most contributors have no
test tenant. All three now ask for any tenant the tester is allowed to test in, with messages and files going only
to accounts the tester controls, and the pull request describing what was tested.
No module file changes, so there is no changelog entry. No live testing was needed.
Release classification
Checklist
develop, ormainfor a hotfixCHANGELOG.mdhas an entry in the right section under[Unreleased](added if missing), or the change is not user-visible.\Tests\Invoke-Tests.ps1passes