PromucFlow_constructor/app/server
Anagh Hegde 2e5ce66680
feat: Add application metadata for branch protection (#27207)
## Description
We already store the default branch information. We can store the
`protectedBranches` as a list of string. Another option is to add a
boolean field to denote whether the branch is protected on not.
Here is how `gitApplicationMetadata` property will look like in the
default branch:
"gitApplicationMetadata": {
    ....
    "branchName": "master",
    "defaultBranchName": "master", 
"branchProtectionRules": ["develop", "master"], // present in default
branch only
    "isProtectedBranch": true, // present in all branches
    "remoteUrl": "git@github.com:nayan-rafiq/merge-test.git",
    ...
}

Here is how `gitApplicationMetadata property` will look like in the
child branches:
"gitApplicationMetadata": {
    ....
    "branchName": "master",
   "defaultBranchName": "master", 
    "isProtectedBranch": true, // present in all branches
    "remoteUrl": "git@github.com:nayan-rafiq/merge-test.git",
    ...
}

#### PR fixes following issue(s)
Fixes https://github.com/appsmithorg/appsmith/issues/27206

#### Type of change
- New feature (non-breaking change which adds functionality)

## Testing

#### How Has This Been Tested?
- [ ] Manual
- [ ] JUnit
- [ ] Jest
- [ ] Cypress
>
>
#### Test Plan
> Add Testsmith test cases links that relate to this PR
>
>
#### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
>
>
>
## Checklist:
#### Dev activity
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag


#### QA activity:
- [ ] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [ ] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [ ] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-09-13 11:38:28 +05:30
..
.run chore: Upgrade to Spring Boot 3.0.1 (#19044) 2023-01-02 19:40:59 +07:00
appsmith-git test: canvas widget coverage junit (#26384) 2023-08-16 22:05:59 +05:30
appsmith-interfaces fix: Skip create application when root application is present (#27099) 2023-09-12 11:09:39 +05:30
appsmith-plugins chore: Remove irrelevant exclusion introduced in #27044 (#27051) 2023-09-07 11:39:08 +05:30
appsmith-server feat: Add application metadata for branch protection (#27207) 2023-09-13 11:38:28 +05:30
envs fix: Updated server set up docs to lower confusion from logs (#22926) 2023-05-03 10:17:34 +05:30
mongo-seed
reactive-caching chore(deps): Update pf4j to v3.10.0 (#27044) 2023-09-07 08:48:45 +05:30
scripts chore: Delete unused app/server/scripts/node 2023-08-08 06:00:48 +05:30
.gitignore
build.sh chore: Check Java version in build script (#19531) 2023-01-06 22:20:58 +05:30
buildpack-run.sh
docker-compose.yml chore: Use new Docker image for dev-time server (#25609) 2023-07-24 09:56:30 +05:30
pom.xml chore(deps): Update pf4j to v3.10.0 (#27044) 2023-09-07 08:48:45 +05:30
Procfile
README.md
system.properties chore: Upgrade to Spring Boot 3.0.1 (#19044) 2023-01-02 19:40:59 +07:00

Appsmith Server

This is the server-side repository for the Appsmith framework.

For details on setting up your development machine, please refer to this Setup Guide.