Configure GitHub Actions to Build Smart Contracts on Push

[Ceejaytech25]

📋 Issue #623: Configure GitHub Actions to Build Smart Contracts on Push

💡 Description & Objective

This issue tracking item focuses on addressing Configure GitHub Actions to Build Smart Contracts on Push 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:

• Create .github/workflows/rust.yml.
• Write jobs performing workspace compiler checks on updates.
• 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-623-configure-github-actions-to-build-s

💬 2. Commit Message Standard

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

feat(devops-ci): configure github actions to build smart contracts on push (closes #623)

Example: feat(devops-ci): configure github actions to build smart contracts on push closes #623

🚀 3. Pull Request Details

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

[YfengJ]

Hi maintainers, I would like to apply for this issue if it is available.

If assigned, I can add a GitHub Actions workflow for the contracts/ sub-workspace that runs cargo check and cargo test on pull requests, using pinned actions and keeping it separate from unrelated backend/dashboard jobs.

I will wait for maintainer or Stellar Wave assignment before starting implementation or opening a PR.

[Goodnessoj]

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

Hi maintainer, I would love to work on this issue

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

[10xwhoman]

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

Hello i would love to work on this.

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

[drips-wave]

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

🧑‍💻 @10xwhoman: 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 🌊

[YfengJ]

Thanks for the update. I see this has been assigned to @10xwhoman, so I will step back and will not work on or open a PR for this issue. Good luck with the implementation.