Push to GitHub

Run unit tests and lint checks before pushing changes to GitHub.

291|148|Updated Apr 2, 2018
One-click install
npx skills add https://github.com/google/ground-android --skill push-to-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Push to GitHub
Source: https://github.com/google/ground-android/tree/main/.agent/skills/push_to_github
Command: npx skills add https://github.com/google/ground-android --skill push-to-github

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill ensures that code changes are validated by running unit tests and lint checks before being pushed to GitHub, acting as a final safety gate to protect CI pipelines.

Core Features & Use Cases

  • Pre-push validation: Runs unit tests locally and performs code quality checks to catch issues early.
  • Safe push workflow: Automatically pushes to the current branch after passing checks, enabling a smooth collaboration flow.
  • Adaptable for Android projects: Tailored for Gradle-based Android apps, but can be extended to other Gradle projects.

Quick Start

Run the push script to perform pre-push checks and push your branch to GitHub.

Frequently Asked Questions about Push to GitHub

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run unit tests and lint checks before a git push?

To run unit tests and lint checks before a git push, you can use a pre-push validation script that automatically executes local Gradle checks and only pushes code to GitHub if all validations pass.

Can I automate Gradle lint checks and unit tests before pushing to GitHub?

Yes, you can automate Gradle lint checks and unit tests before pushing to GitHub by running a local validation script that acts as a safety gate to catch code quality issues early.

What is the best way to prevent failing code from reaching CI pipelines?

The best way to prevent failing code from reaching CI pipelines is to run local pre-push checks, executing unit tests and lint validations before allowing changes to be pushed to GitHub.

Does pre-push validation work with Gradle-based Android projects?

Pre-push validation works with Gradle-based Android projects and can be extended to other Gradle workflows to perform unit tests, lint checks, and safe branch pushing.

Why should I run local validation checks before pushing changes?

You should run local validation checks before pushing changes because it acts as a final safety gate to catch code quality issues early, protecting your CI pipelines from failing.