ci(workflow): add common workflows for Android and Python, including CI /CD revamp#422
Conversation
There was a problem hiding this comment.
Pull Request Overview
This pull request consolidates and modernizes the CI/CD workflows for both Android and Python components of the project. It introduces reusable GitHub Actions, streamlines workflow organization, and establishes consistent patterns across the repository.
- Consolidated multiple individual Android workflows into a single comprehensive
android-ci.ymlworkflow - Replaced the existing Python workflow with new
python-ci.ymland updatedpython-cd.ymlworkflows - Added reusable composite actions for common setup tasks and centralized configuration files
Reviewed Changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
AGENTS.md |
Added comprehensive repository guidelines covering project structure, build commands, coding standards, and development workflows |
.java-version |
Added Java 21 version specification for consistent tooling |
.github/workflows/python-ci.yml |
New comprehensive Python CI workflow with dependency review, CodeQL analysis, linting, and testing |
.github/workflows/python-cd.yml |
Updated Python CD workflow to use the new reusable action and simplified token handling |
.github/workflows/greeting.yml |
Minor updates to workflow name and job naming |
.github/workflows/gradle-wrapper-validation.yml |
Removed standalone wrapper validation (now part of android-ci) |
.github/workflows/gradle-dokka.yml |
Removed standalone documentation generation (now part of android-ci) |
.github/workflows/emoji-generator-ci.yml |
Removed old Python workflow (replaced by python-ci) |
.github/workflows/android-unit-test.yml |
Removed standalone unit test workflow (now part of android-ci) |
.github/workflows/android-spotless.yml |
Removed standalone spotless workflow (now part of android-ci) |
.github/workflows/android-publish-artifact.yml |
Removed standalone artifact publishing (now part of android-ci) |
.github/workflows/android-ci.yml |
New consolidated Android CI workflow combining all previous Android workflows |
.github/actions/python/action.yml |
New reusable composite action for Python environment setup |
.github/actions/android/action.yml |
New reusable composite action for Android environment setup |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
2dd0a30 to
c56f1c7
Compare
c56f1c7 to
2346d7c
Compare
…CI /CD revamp (#422) * ci(workflow): add common workflows for Android and Python, including CI /CD revamp * ci(workflow): ignore python CI workflow in push and pull request triggers * ci(actions): add caching for Gradle dependencies in Android workflow * ci(workflow): update python CI workflow to include additional paths and job names * ci(workflow): standardize workflow names to title case * ci(workflow): seperate lint job, format and type checks
AniTrend Pull Request
Thank you for contributing! Please take a moment to review our contributing guidelines to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that add a new library or change existing tests, otherwise you risk spending a lot of time working on something that might not end up being merged into the project.
Before opening a pull request, please ensure you've done the following:
developand targetsdevelop(where applicable)Types of changes
IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the terms of the Apache License 2.0.