[Feature]: Provide stable and develop versions for resiliency
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the CLI and settings entry points that control how the tool identifies its version. Define what stable versus develop should mean for users and how the build badge or version selection should reflect that; the issue provides no named files or tests.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently the build badge shows that the build process is failing. As a user who maybe dependent on this tool, I need to be able to have a stable version of the tool.
Describe the solution you'd like
Building a flag into the CLI or settings to allow a user to identify if they are wanting stable vs develop (think Microsoft Edge) will help with risk adverse/critical workloads.
Describe alternatives you've considered
No response
Additional context?
No response
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-TestEngine
-
new
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
new
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
new
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/PowerApps-TestEngine
Similar issues
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
aws/aws-dotnet-ai#75 ·