[Feature]: Remove GitHub Actions Workflows

[SudiptaPaul-31]

🔍 Problem Statement

📖 Description

Due to severe problems with the current GitHub Actions setup (e.g., unreliable builds, failing checks, or misconfigured workflows), we need to remove all GitHub Actions workflows from the repository. This will prevent contributors and maintainers from being blocked by broken CI/CD pipelines until a stable replacement is introduced.

Expected Behavior

• All existing GitHub Actions workflow files (e.g., .github/workflows/*.yml) should be removed.
• Repository should no longer trigger GitHub Actions on PRs, commits, or merges.
• Contributors and maintainers should not see failing GitHub Actions checks on new pull requests.

🛠 Technical Notes

• Identify and delete all workflow files under .github/workflows/.
• Confirm that no references to GitHub Actions remain in repository settings.
• Document removal in the changelog or README for transparency.
• Consider planning for a future CI/CD solution (e.g., alternative pipelines or manual build instructions).

✅ Acceptance Criteria

• No GitHub Actions workflows exist in the repository.
• PRs and commits no longer trigger GitHub Actions checks.
• npm run lint and npm run build still succeed locally.
• Contributors and maintainers are not blocked by failing CI/CD checks.

📈 Expected Impact

High — Would significantly improve user experience

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I'd like to handle this. Thanks

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

[drips-wave]

Congratulations, @SamixYasuke! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @SamixYasuke: 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 issued 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 🌊

[SamixYasuke]

On it

[drips-wave]

This issue has been completed by @SamixYasuke as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @SamixYasuke: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.