Context
Currently, Casper Node development employs Drone for continuous integration and Bors for pull request merging. This setup, while functional, can benefit from more seamless integration and automation capabilities provided by GitHub Actions and GitHub Merge Queue. Integrating these tools can enhance the development process, streamline CI/CD pipelines, and improve merge efficiencies.
Goal
The goal of this task is to create a proof of concept (PoC) for replacing Drone with GitHub Actions for CI/CD workflows and Bors with GitHub Merge Queue for managing pull request merges. This PoC should validate the feasibility and benefits of transitioning to these GitHub-native solutions while maintaining or improving current workflow efficiencies.
Requirements
Configure GitHub Actions to replicate CI/CD workflows currently handled by Drone.
Set up GitHub Merge Queue to manage pull request merges, replacing Bors.
Context Currently, Casper Node development employs Drone for continuous integration and Bors for pull request merging. This setup, while functional, can benefit from more seamless integration and automation capabilities provided by GitHub Actions and GitHub Merge Queue. Integrating these tools can enhance the development process, streamline CI/CD pipelines, and improve merge efficiencies.
Goal The goal of this task is to create a proof of concept (PoC) for replacing Drone with GitHub Actions for CI/CD workflows and Bors with GitHub Merge Queue for managing pull request merges. This PoC should validate the feasibility and benefits of transitioning to these GitHub-native solutions while maintaining or improving current workflow efficiencies.
Requirements