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

[ERC Registry] Phase 3: Add a dedicated CI workflow for ERC Registry tool #1167

Closed
Tracked by #1107
quiet-node opened this issue Jan 13, 2025 · 0 comments · Fixed by #1168
Closed
Tracked by #1107

[ERC Registry] Phase 3: Add a dedicated CI workflow for ERC Registry tool #1167

quiet-node opened this issue Jan 13, 2025 · 0 comments · Fixed by #1168
Assignees
Labels
internal For changes that affect the project's internal workings but not its outward-facing functionality.
Milestone

Comments

@quiet-node
Copy link
Member

quiet-node commented Jan 13, 2025

Description

The ERC Registry tool currently lacks a CI workflow, which limits visibility into the impact of code changes.

Solution

Introduce a dedicated CI workflow to run unit tests and acceptance tests for the ERC Registry tool.

@quiet-node quiet-node self-assigned this Jan 13, 2025
@quiet-node quiet-node added the internal For changes that affect the project's internal workings but not its outward-facing functionality. label Jan 13, 2025
@quiet-node quiet-node moved this from Backlog to Tasks In Progress in Smart Contract Sprint Board Jan 13, 2025
@quiet-node quiet-node added this to the 0.12.0 milestone Jan 13, 2025
@quiet-node quiet-node linked a pull request Jan 13, 2025 that will close this issue
2 tasks
@quiet-node quiet-node moved this from Tasks In Progress to In Review in Smart Contract Sprint Board Jan 13, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in Smart Contract Sprint Board Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal For changes that affect the project's internal workings but not its outward-facing functionality.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant