microsoft / microsoft/msix-packaging
[BUG/FEATURE REQUEST] MSIX packaging extension for Azure DevOps release - Configuration combo should not be restricted to 2 values
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Project
MSIX SDK or Win7Msix
Describe the bug
On Azure DevOps extension, the configuration option had only 2 values 'Debug' and 'Release'.
To Reproduce
Install the devops extenstion, create a package task
Expected behavior
Configuration should allow to set any value. Configuration can't be standard accross company and now, you tend to have development/staging/production instead of Debug/Release as default configuration
Is this something you can fix?
Thanks,
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the Azure DevOps extension's package task configuration and inspect where the Configuration option is limited to Debug and Release. Confirm how custom values are validated, then verify that development, staging, production, and other arbitrary values are accepted when creating and running the package task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100