-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow improvements and enhancements 🍭 #66
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added the `autolabeler` for auto labeling PRs * Update and change the description template
* Changed the label name: `deprecated` -> `deprecate` * Changed the title name for new features and enhancements
This change updated the autolabeler to labeling PRs on the following conditions: - Some changes on Python code -- `lang:python` - Some changes on Java code -- `lang:java`
* Now the `codeql` will only checks if the following statements are true: - Changed files are inside `src` directory - Changed files are type of Java or Python files * Changed the `develop` -> `release` branch We should check the codes before get pushed to `release` branch then releasing the new version. Beside that, from now on the `develop` branch very rarely active, instead use the `master` branch for any PRs and future changes.
* Now `pylint` only uses Python v3.7 and the latest one to check the codes. * Now the workflow will create cache for installed dependencies * PyLint are now will performs on both Ubuntu and Windows platform
This change introduces several modifications to the `codeql` workflow: - The workflow has been reconfigured to exclude Python setup and analysis. - CodeQL analysis now covers both Ubuntu and Windows platforms to ensure code portability. - The cache step has been configured to store installed Maven dependencies, improving workflow efficiency. It's worth noting that the analysis of Python code has been moved to the PyLint workflow. Additionally, JMatrix's public APIs are primarily built in Java, emphasizing stability, portability, and security. This shift allows us to focus on enhancing the quality of the Java-based public APIs.
* Changed the workflow name * Added description about the workflow
mitsuki31
commented
Aug 11, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mitsuki31
force-pushed
the
maintenance/improve-workflows
branch
from
August 12, 2023 10:13
bc03153
to
4e8aecb
Compare
This workflow runs on 3 conditions: - Push - Pull request (PR) - Manual This workflow designed for testing the project with the supported builder (`Maven` and `Make`) and and help to find issues in the project code more easier.
mitsuki31
force-pushed
the
maintenance/improve-workflows
branch
from
August 12, 2023 10:42
4e8aecb
to
be91b08
Compare
* Now the workflow only runs when the specified files are changed (only push). * Introduced a debug option for the packaging step to aid in troubleshooting. * Addressed limitations in Make's testing capabilities by focusing on compiling, packaging, and generating docs. * The changes aim to enhance project testing, packaging, and documentation processes while allowing for debugging when needed.
* Remove unnecessary code on Make Test. * Now the Maven Test will also clean up the project.
mitsuki31
force-pushed
the
maintenance/improve-workflows
branch
from
August 18, 2023 15:09
baa85e5
to
f286b32
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request focuses on refining and enhancing various workflows within the project to streamline processes and improve code quality.
Changes Made
Release Drafter Workflow
autolabeler
to automatically label pull requests (PRs).Updated the autolabeler to apply labels to PRs based on specific conditions:
lang:python
.lang:java
.deprecate
for labeling the deprecated features on PRs (similar withremove
).CodeQL Workflow
develop
torelease
, ensuring code is thoroughly checked before being pushed to therelease
branch.PyLint Workflow
VirusTotal Scan Workflow
Dependabot Workflow
Project Tester Workflow
tests.yml
).jmatrix/.github/workflows/tests.yml
Lines 6 to 9 in 315f568
workflow_dispatch
(run manually).jmatrix/.github/workflows/tests.yml
Lines 14 to 21 in 315f568
All Commits
codeql
workflowpylint
workflowcodeql
workflow and cachingvirus-scan.yml
tests
Description
This pull request encompasses a series of workflow enhancements aimed at improving code quality, workflow efficiency, and overall project stability. These changes optimize the release process, streamline code analysis, and emphasize the use of Java for public APIs to ensure robustness, portability, and security.
Summary
Enhancements and refinements have been made to various workflows, such as Release Drafter, CodeQL, VirusTotal Scan, and other workflows to bolster the project's development processes and ensure code quality and security.