aws-amplify / aws-amplify/amplify-hosting
Exclude specific branches detection not working in Amplify
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Environment information
```plain text
I am trying to exclude develop, release, prod branches and remaining all branches need to be detect in Amplify but it is not working exclude detect branches.
*,!release,!prod,!develop (noticed after save it is moving automatically order like this !release,!prod,!develop,*) - Not working exclude branches
"*","!release","!develop","!prod" - Noticed after save it is changing order like this "!develop","!prod","!release","*" - Not working exclude branches
How to exclude specific branches and remaining all branches need to include for auto detect in Amplify?
```
### Describe the bug
I am trying to exclude develop, release, prod branches and remaining all branches need to be detect in Amplify but it is not working exclude detect branches.
*,!release,!prod,!develop (noticed after save it is moving automatically order like this !release,!prod,!develop,*) - Not working exclude branches
"*","!release","!develop","!prod" - Noticed after save it is changing order like this "!develop","!prod","!release","*" - Not working exclude branches
How to exclude specific branches and remaining all branches need to include for auto detect in Amplify?
### Reproduction steps
I am trying to exclude develop, release, prod branches and remaining all branches need to be detect in Amplify but it is not working exclude detect branches.
*,!release,!prod,!develop (noticed after save it is moving automatically order like this !release,!prod,!develop,*) - Not working exclude branches
"*","!release","!develop","!prod" - Noticed after save it is changing order like this "!develop","!prod","!release","*" - Not working exclude branches
How to exclude specific branches and remaining all branches need to include for auto detect in Amplify?
Contributor guide
Research direction
No repository file, test, or entry point is named. Start by reproducing the branch-pattern behavior in AWS Amplify Hosting with the configurations shown; done means confirming a supported pattern that excludes develop, release, and prod while automatically detecting all other branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100