Hcx communication #8178
Hcx communication #8178
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for care-egov-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
CARE
|
||||||||||||||||||||||||||||
| Project |
CARE
|
| Branch Review |
hcx-communication
|
| Run status |
|
| Run duration | 02m 57s |
| Commit |
|
| Committer | Khavin Shankar |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
0
|
Skipped
|
0
|
Passing
|
126
|
| View all changes introduced in this branch ↗︎ | |
|
@khavinshankar can you update the PR description for review purpose to understand what changed in this PR |
|
👋 Hi, @khavinshankar, This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there. |
|
👋 Hi, @khavinshankar, This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there. |
|
As the issues mentioned above involve working on the entire HCX module, it will be tackled in a separate PR and will be monitored in a new issue #8413. This way HCX Communication flow is not blocked for merging. Ideally the above-mentioned issues will be tackled along with HCX plug seperation. |
|
👋 Hi, @khavinshankar, This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there. |
|
👋 Hi, @khavinshankar, This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there. |
|
@khavinshankar can you get this PR ready for review and testing |
|
@khavinshankar is this required in the context of NHCX? |
|
Let's close it 🚀 |
|
Closing based on confirmation from @khavinshankar |
Added HCX communication flow
Backend PR: ohcnetwork/care#1346
Further docs will be added later in docs repo