Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start Looking at Switching To Azure Feeds #3532

Conversation

michael-hawker
Copy link
Member

Fixes #3184

First step, sets up having specific versions per PR so we can create separate release pipelines for a dedicated PR feed in addition to our CI feed.

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tested code with current supported SDKs
  • Pull Request has been submitted to the documentation repository instructions. Link:
  • Sample in sample app has been added / updated (for bug fixes / features)
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Header has been added to all new source files (run build/UpdateHeaders.bat)
  • Contains NO breaking changes

Other information

@ghost
Copy link

ghost commented Oct 17, 2020

Thanks michael-hawker for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

@michael-hawker michael-hawker added this to the 7.0 milestone Oct 17, 2020
@ghost ghost requested review from azchohfi and Kyaa-dost October 17, 2020 00:13
@ghost ghost added feature request 📬 A request for new changes to improve functionality improvements ✨ labels Oct 17, 2020
@michael-hawker michael-hawker added build 🔥 CI/pipeline 🔬 and removed feature request 📬 A request for new changes to improve functionality improvements ✨ labels Oct 17, 2020
@michael-hawker michael-hawker force-pushed the mhawker/move-to-azurefeeds branch 5 times, most recently from 098deec to 972e0a5 Compare October 19, 2020 23:40
@michael-hawker michael-hawker force-pushed the mhawker/move-to-azurefeeds branch from 972e0a5 to 40eb7c7 Compare October 20, 2020 00:06
@michael-hawker
Copy link
Member Author

Think for now everything will happen in the release step of the pipeline, so we don't need these changes (which didn't work anyway...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] Move from MyGet to Azure or GitHub Packaging Solution
1 participant