WIP: DONOT MERGE Staging to Production merge#67
Conversation
Added routes for validating the project name and unit tests for the same
removed unnecessary pass statement
Feature local setup
Added detailed deployment architecture and services information to README.
Expand README with deployment architecture and services
Readme updated with steps to run local development
Update README.md
Deploying the required code
Updated unit tests for CORS
- Added notes to local development. - Need to add more details on initial development.
Migration logic yet to be written
Added routes for validating the project name and unit tests for the same
removed unnecessary pass statement
Added detailed deployment architecture and services information to README.
Readme updated with steps to run local development
Develop to Stage merge
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hey both, I took a look at this PR cursorily, it looks reasonable--I mean, staging is pretty far ahead of production, so I expected this to be a big one. I didn't see anything obviously off. Re: why the conflicts, great question. I'm guessing this is because Cy applied his changes in prod only, and our staging PR includes those too, but maybe not exactly in the same order. So my expectation is that as Naresh said, yes, we can force push staging to prod and end up in the same place as we are now + have Tasking Manager. But yes, only do this after 7/28 when Anat's done with the demos. Thanks both! |
Merge from staging to production
Discuss before merging it.