Configure Automated Cleanup of Test Artifacts in CI

[Ceejaytech25]

📋 Issue #630: Configure Automated Cleanup of Test Artifacts in CI

💡 Description & Objective

This issue tracking item focuses on addressing Configure Automated Cleanup of Test Artifacts in CI within the devops-ci component scope. Contributors should follow the detailed guidelines below to implement, document, and test the solution correctly.

---

🛠️ Step-by-Step Implementation Guide

To solve this issue, please proceed as follows:

• Deploy cleaning workflows hooks executing post-tests steps.
• Ensure formatting rules are respected before pushing.

---

🧪 Local Validation

Validate your changes locally by running:

git diff

---

🤝 Contribution Guidelines

🌿 1. Branch Naming Rules

Create a new branch from main using the following exact format:

feature/issue-630-configure-automated-cleanup-of-test

💬 2. Commit Message Standard

Use Conventional Commits format when creating commits. Your final commit (or PR squash commit) must include:

feat(devops-ci): configure automated cleanup of test artifacts in ci (closes #630)

Example: feat(devops-ci): configure automated cleanup of test artifacts in ci closes #630

🚀 3. Pull Request Details

• Ensure all tests pass locally.
• Do not commit local SQLite files or lock files.
• Submit your branch for peer review.

[Samaro1]

@Samaro1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Gm gm boss, I would love to work on this issue. A satisfactory and efficient PR will be raised

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samaro1 to this issue.

[dot-enny]

@dot-enny has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, i can take care of this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dot-enny to this issue.

[Olamidepy]

@Olamidepy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer,

I would love to be assigned to this issue.

I’m a Full-Stack Developer and I also actively explore blockchain development and smart contracts, which has strengthened my problem-solving skills and attention to code quality.

After reviewing the issue, I believe I can contribute effectively and deliver a well-tested solution within the expected standards of the project.

ETA: 6 hours

Thank you for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Olamidepy to this issue.

[drips-wave]

Congratulations, @Olamidepy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Olamidepy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊