Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull "main" branch to develop for new branching strategy #6281

Closed
wants to merge 320 commits into from

Conversation

dakotabenjamin
Copy link
Member

@ramyaragupathy this is an example pull request that could be made to prepare a deployment.

First all PRs should be made to "develop" which will be deployed to the dev servers

Then when preparing for a deployment, a PR should be made like this one, develop onto main. Merging this will deploy to staging and the PR can serve as a useful commit history for the release notes.

tsmock and others added 30 commits November 27, 2023 09:22
Signed-off-by: Taylor Smock <[email protected]>
… for some of those functions

Signed-off-by: Taylor Smock <[email protected]>
- Increase API Backend load balancer timeout from 60s to 180s
- Bump PostgreSQL engine version for AWS RDS from 11.19 to 13.10
- Cleanup unused Route53 entry (must be removed)
- Enable HTTP/2 in API Backend load balancer explicitly (no infra
  change)
- Add experimental dummy Route53 entries to new tasks.hotosm.org hosted
  zone. Both A and AAAA resource records are added
…/semver-5.7.2

Bump semver from 5.7.1 to 5.7.2 in /frontend
…/word-wrap-1.2.4

Bump word-wrap from 1.2.3 to 1.2.4 in /frontend
…/browserify-sign-4.2.2

Bump browserify-sign from 4.2.1 to 4.2.2 in /frontend
Bumps [@adobe/css-tools](https://github.com/adobe/css-tools) from 4.0.1 to 4.3.2.
- [Changelog](https://github.com/adobe/css-tools/blob/main/History.md)
- [Commits](https://github.com/adobe/css-tools/commits)

---
updated-dependencies:
- dependency-name: "@adobe/css-tools"
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@robsavoye
Copy link
Collaborator

Since there are many old PRs for the main branch, which nobody has used for quite a while,
I think recreating it from the current develop branch is the way to go. We'd then keep this stable main branch which would be used for deployments. All new PRs would go into the develop branch and tested on the dev server.

@ramyaragupathy
Copy link
Member

Agree with @robsavoye - we will create a new main branch out of existing develop.

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@dakotabenjamin dakotabenjamin deleted the branch main March 26, 2024 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file scope: translations
Projects
None yet
Development

Successfully merging this pull request may close these issues.