feat(project): merge to develop for release QA#5773
Conversation
…nding Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…ct-detail Signed-off-by: Wanjin Noh <wanjin@megazone.com>
Signed-off-by: Wanjin Noh <wanjin@megazone.com>
Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…ove UI and functionality Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…ved dashboard handling Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…ed directory Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…amic elements Signed-off-by: Wanjin Noh <wanjin@megazone.com>
Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…nalysis features Signed-off-by: Wanjin Noh <wanjin@megazone.com>
…ct-detail Signed-off-by: Wanjin Noh <wanjin@megazone.com>
… name convention Signed-off-by: samuel.park <samuel.park@megazone.com>
…ice (dashboard create only) Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
…il page Signed-off-by: samuel.park <samuel.park@megazone.com>
…ard components Signed-off-by: samuel.park <samuel.park@megazone.com>
…board service Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
… composables Signed-off-by: samuel.park <samuel.park@megazone.com>
…roject-dashboard query Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
feat(dashboard): separate dashboard shared from dashaboards service & edit project route
…egration-project-detail Signed-off-by: NaYeong,Kim <nayeongkim@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: piggggggggy <samuel.park@mz.co.kr>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
…egration-project-detail Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
Signed-off-by: samuel.park <samuel.park@megazone.com>
…egration-project-detail Signed-off-by: samuel.park <samuel.park@megazone.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
✅ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO. Contributors sign-off that they adhere to these requirements by adding a Git even has a |
Signed-off-by: samuel.park <samuel.park@megazone.com>
|
✅ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO. Contributors sign-off that they adhere to these requirements by adding a Git even has a |
Skip Review (optional)
style,chore,ci,test,docs)Description (optional)
Things to Talk About (optional)