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

Open
geospatialem opened this issue Sep 16, 2024 · 0 comments
Assignees
Labels
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. p - low Issue is non core or affecting less that 10% of people using the library spike Issues that cannot be estimated well enough until the team has done further research 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 cannot be estimated well enough until the team has done further research 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. p - low Issue is non core or affecting less that 10% of people using the library spike Issues that cannot be estimated well enough until the team has done further research tooling Issues relating to build system fixes or improvements.
Projects
None yet
Development

No branches or pull requests

2 participants