Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Document @changesets/cli integration with Azure DevOps release pipelines
See original GitHub issueAffected Packages
@changesets/cli
Problem
My company doesn’t use Github, so Github actions won’t work for me. However, we use Azure DevOps for CI, so it’d be great to have an action/job/task or even a script to use in that environment for provide the same or similar functionality for our build/release environments.
Proposed solution
It’d be good to update the “CI” section of the docs to include the bare minimum manual steps or scripts required to work with the @changesets/cli nicely.
Ideally the Github action would be ported to Azure DevOps to update PRs, leave comments, etc. if that’s possible in that world.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:9
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Has anybody succeeded in consuming changesets on Azure DevOPs (ADO) pipeline ?
working with azure devops: anyone here is aware of a way to keep changesets and still be able to fail a pr if a developer did not add a changeset for his code. ( “since-master” will not work because it sees others’s stored changesets)