Skip to content

chore: merge develop to master #5741

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.

Sign up for GitHub

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

Jump to bottom
Merged
yuda110 merged 6 commits into from
Apr 4, 2025
Merged

chore: merge develop to master #5741

yuda110 merged 6 commits into from
Apr 4, 2025

Conversation

@yuda110
Copy link
Member

@yuda110 yuda110 commented Apr 4, 2025

Skip Review (optional)

  • Minor changes that don't affect the functionality (e.g. style, chore, ci, test, docs)
  • Previously reviewed in feature branch, further review is not mandatory
  • Self-merge allowed for solo developers or urgent changes

Description (optional)

Things to Talk About (optional)

admin-cloudforet and others added 6 commits April 3, 2025 03:19
@admin-cloudforet
chore: merge master into develop after 2.0.dev340 version tagging
e863af2
@admin-cloudforet
chore: merge master into develop after 2.0.dev341 version tagging
50690a6
@piggggggggy
chore(route-config): fix wrong route config usage (#5737)
eca2952 
Signed-off-by: samuel.park <samuel.park@megazone.com>
@admin-cloudforet
chore: merge master into develop after 2.0.dev342 version tagging
1daba1f
@yuda110
feat: do not hide search when there're no menu (#5740)
96c50e9 
Signed-off-by: yuda <yuda@megazone.com>
@yuda110
feat: update task when its' TODO & add 'Task ID' field, filter to Tic…
1512321 
…ket Board (#5738)

* feat: update task when its' TODO

Signed-off-by: yuda <yuda@megazone.com>

* feat: add 'Task ID' field, filter to Ticket Board

Signed-off-by: yuda <yuda@megazone.com>

* chore: update language

Signed-off-by: yuda <yuda@megazone.com>

* fix: add `taskId` to `TaskManagementTemplate`

Signed-off-by: yuda <yuda@megazone.com>

* refactor: separate update and updateDescription APIs

Signed-off-by: yuda <yuda@megazone.com>

* refactor: use `isEditable` getters from task-content-form-store

Signed-off-by: yuda <yuda@megazone.com>

* chore: use dynamic translation to 'Task ID'

Signed-off-by: yuda <yuda@megazone.com>

* chore: fix wrong template id

Signed-off-by: yuda <yuda@megazone.com>

---------

Signed-off-by: yuda <yuda@megazone.com>
@vercel
Copy link

vercel bot commented Apr 4, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
console 🔄 Building (Inspect) Visit Preview Apr 4, 2025 3:04am
web-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 4, 2025 3:04am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
dashboard ⬜️ Ignored (Inspect) Apr 4, 2025 3:04am
feature-project-landing ⬜️ Ignored (Inspect) Apr 4, 2025 3:04am

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2025

⚠️ @yuda110 the signed-off-by was not found in the following 3 commits:

  • e863af2: chore: merge master into develop after 2.0.dev340 version tagging
  • 50690a6: chore: merge master into develop after 2.0.dev341 version tagging
  • 1daba1f: chore: merge master into develop after 2.0.dev342 version tagging

✅ Why it is required

The 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 Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2025

✅ There are no commits in this PR that require review.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2025

🎉 @skdud4659 and @piggggggggy have been randomly selected as the reviewers! Please review. 🙏

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2025

⚠️ @yuda110 the signed-off-by was not found in the following 3 commits:

  • e863af2: chore: merge master into develop after 2.0.dev340 version tagging
  • 50690a6: chore: merge master into develop after 2.0.dev341 version tagging
  • 1daba1f: chore: merge master into develop after 2.0.dev342 version tagging

✅ Why it is required

The 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 Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

@yuda110 yuda110 merged commit 9b9a5f5 into master Apr 4, 2025
12 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@piggggggggy piggggggggy Awaiting requested review from piggggggggy

@skdud4659 skdud4659 Awaiting requested review from skdud4659

Assignees

@yuda110 yuda110

Labels

fail/signedoff

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@yuda110 @admin-cloudforet @piggggggggy