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

[Tooling] Setup automation to remove a design project once marked as ready for dev #10327

Closed
geospatialem opened this issue Sep 16, 2024 · 4 comments
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. estimate - 5 A few days of work, definitely requires updates to tests. p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.

Comments

@geospatialem
Copy link
Member

Priority impact

p - low

Summary

To simplify our processes and streamline the way we track design issues in projects we should explore and if possible, adopt removing the project via Actions.

Desired Outcome

Removes the design project from the issue when the ready for dev label is added.

Resources

@geospatialem geospatialem added tooling Issues relating to build system fixes or improvements. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. labels Sep 16, 2024
@github-actions github-actions bot added the p - low Issue is non core or affecting less that 10% of people using the library label Sep 16, 2024
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. estimate - 5 A few days of work, definitely requires updates to tests. and removed 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Sep 16, 2024
@DitwanP DitwanP added 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Oct 30, 2024
@DitwanP DitwanP removed the spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. label Jan 13, 2025
DitwanP added a commit that referenced this issue Jan 16, 2025
**Related Issue:** #10327 

## Summary
Action that will remove issues from respective projects after design
team has marked them with the `ready for dev` label.
@DitwanP DitwanP added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Jan 16, 2025
Copy link
Contributor

Installed and assigned for verification.

@DitwanP DitwanP added the ready for dev Issues ready for development implementation. label Jan 16, 2025
@github-actions github-actions bot added 0 - new New issues that need assignment. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. labels Jan 16, 2025
Copy link
Contributor

cc @geospatialem, @brittneytewks

@calcite-admin
Copy link
Contributor

The issue has been removed from the Calcite Design Effort 2025-12-16 Dec project.

@DitwanP DitwanP added 4 - verified Issues that have been released and confirmed resolved. and removed 0 - new New issues that need assignment. 3 - installed Issues that have been merged to master branch and are ready for final confirmation. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. ready for dev Issues ready for development implementation. labels Jan 16, 2025
@DitwanP DitwanP self-assigned this Jan 16, 2025
@DitwanP
Copy link
Contributor

DitwanP commented Jan 16, 2025

Verified

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. estimate - 5 A few days of work, definitely requires updates to tests. p - low Issue is non core or affecting less that 10% of people using the library tooling Issues relating to build system fixes or improvements.
Projects
None yet
Development

No branches or pull requests

3 participants