jacoco-badge-generator
awesome-readme
jacoco-badge-generator | awesome-readme | |
---|---|---|
16 | 30 | |
92 | 16,961 | |
- | - | |
7.5 | 6.9 | |
28 days ago | 6 days ago | |
Python | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jacoco-badge-generator
-
jacoco-badge-generator 2.11.0 Released
jacoco-badge-generator - Coverage badges, and pull request coverage checks, from JaCoCo reports in GitHub Actions
-
jacoco-badge-generator 2.10.0 Released
I just released jacoco-badge-generator 2.10.0, which can be run as a GitHub Action or as a command-line utility as part of CI/CD workflows for Java projects, as well as for projects in other JVM languages such as Kotlin, to parse JaCoCo test coverage reports, generate instructions coverage and branches coverage badges for project READMEs, serve as pull-request checks (e.g., validate minimum coverage thresholds), among other functionality.
-
JaCoCo Coverage Badges for Multi-Module Projects in GitHub Actions
I just release version v2.9.0, which enhanced the existing functionality associated with using the jacoco-badge-generator GitHub Action with multi-module projects. Specifically, prior to this release, for a multi-module project, the paths to all of the JaCoCo csv reports had to be listed in the inputs to the action. Now, as of v2.9.0, you can use a glob pattern to specify the paths to the JaCoCo csv reports. This can actually now also work for the more common single module project, but the glob functionality is likely most useful in the multi-module case. Note that the CLI mode already implicitly supported globs since your shell will expand any globs you specify on the command line. But as a GitHub Action this previously was not the case as GitHub Actions doesn't expand globs in the inputs to an Action. The jacoco-badge-generator v2.9.0 now handles glob expansion internally.
-
Automate Updating Major Release Tag on New Releases of a GitHub Action
Vincent Cicirello - Open source GitHub Actions for workflow automation
-
How to Write to Workflow Job Summary from a GitHub Action
I maintain several GitHub Actions implemented in Python as container actions. One of these, jacoco-badge-generator, produces coverage badges from JaCoCo test coverage reports. Additionally, it outputs the test coverage percentages to the workflow job summary. This example is based upon the approach I use in jacoco-badge-generator.
-
Bonus Tip: How to Use GitHub Actions to Test a GitHub Action Whose Output Must be Visually Inspected
Check out all of our GitHub Actions: https://actions.cicirello.org/
-
How to Test a GitHub Action with GitHub Actions
I maintain several GitHub Actions, all of which are implemented in Python as container actions. This post explains how to test a GitHub Action using a GitHub Actions workflow, including using the workflow as a required check on Pull Requests. Although some of this post is specific to testing an action that is implemented in Python, much of the post is more generally applicable to testing actions regardless of implementation language.
-
Using GitHub Actions to Build a Java Project With Pull Request Coverage Commenting and Coverage Badges
The jacoco-badge-generator generates badges, but does not commit them. In this step, I just use a simple shell script to commit and push the badges. This step is conditional and runs only if the event that started the workflow is not a pull request (see the if: ${{ github.event_name != 'pull_request' }}). In other words, it runs on push and workflow_dispatch events. The coverage badges should be consistent with the state of the default branch, so committing badges that correspond to the coverage of a pull request that may or may not be merged doesn't make sense. If it is merged, the push event will then cause the workflow to run again, at which point the coverage badges will be committed. This step begins by changing the current directory to the directory where the badges branch was checked out. And it commits and pushes only if an svg or json file changed. The badges are SVGs, and recall the earlier step where I configured the jacoco-badge-generator to additionally generate a simple JSON file containing the coverage percentages.
-
How to Patch the Deprecated set-output in GitHub Workflows and in Container Actions
There are two primary ways of implementing a GitHub Action: JavaScript Actions and Container Actions. The latter of which enables implementing Actions in any language via a Docker container. My language of choice for implementing GitHub Actions is Python. The purpose of most of these actions is to produce files (e.g., jacoco-badge-generator produces test coverage badges as SVGs, and generate-sitemap produces an XML sitemap) or to edit files in some way (e.g., javadoc-cleanup can insert canonical links and other user-defined elements into the head of javadoc pages). However, all of these also produce workflow step outputs. For example, generate-sitemap has outputs for the number of pages in the sitemap, and the number of pages excluded from the sitemap due to noindex or robots.txt exclusions; and jacoco-badge-generator has workflow step outputs for the coverage and branches coverage percentages if a user had some reason to use those in later steps of their workflow.
-
The user-statistician GitHub Action mentioned in Awesome-README
Vincent Cicirello - Open source GitHub Actions for workflow automation
awesome-readme
- Readme: A Curated List of READMEs
- Awesome Readme: A Curated List of READMEs
-
Hacktoberfest 2023 Update from Maintainer of the user-statistician GitHub Action
About user-statistician
-
Hacktoberfest 2023 Contributors Wanted: Additional Translations for the user-statistician GitHub Action
The user-statistician GitHub Action can generate an SVG with a detailed summary of your activity on GitHub. It is mentioned in the tools section of the awesome README awesome list. The SVG it generates includes general information about you (e.g., year you joined, number of followers, number you are following, most starred repository, etc), information about your repositories (e.g., numbers of stars and forks, etc), information about your contributions (e.g., numbers of commits, issues, PRs, etc), and the distribution of languages within your public repositories.
- Mastering Readme Files
-
Marketing for Developers
If you really want a stellar README.md take a look at some of the examples in awesome-readme for inspiration!
-
How to Create the Best README for Your GitHub Project
Awesome README - A collection of high-quality READMEs from a variety of projects, organized by topic. https://github.com/matiassingers/awesome-readme
-
How to create projects for myself to enrich my resume?
Provide a succinct and comprehensive README: readers of your personal project will always start with the README to know where to begin. The goal of the README is to provide the reader an understanding of the business problem you are trying to solve, how your solution goes about solving it (solution architecture diagram), and how to get started and run your code. There are plenty of great README examples here: https://github.com/matiassingers/awesome-readme
-
Configuring GitHub's Linguist to Improve Repository Language Reporting
About user-statistician
-
The user-statistician GitHub Action mentioned in Awesome-README
Recently, the user-statistician GitHub Action was added to the tools section of Awesome README, which is an Awesome List that includes a curated collection of examples of Awesome READMEs from open source projects, as well as tools enabling creating Awesome READMEs. The Awesome README list is a great place to go if you are looking for ideas for how to improve the READMEs of your open source projects. The Awesome README list covers READMEs more generally, but the tools section includes a few tools focused on Profile READMEs, in addition to many tools for project READMEs more generally. The user-statistician GitHub Action is in the Tools Section.
What are some alternatives?
upload-artifact
revo-grid - Powerful virtual data grid smartsheet with advanced customization. Best features from excel plus incredible performance 🔋
checkout - Action for checking out a repo
Konva - Konva.js is an HTML5 Canvas JavaScript framework that extends the 2d context by enabling canvas interactivity for desktop and mobile applications.
Chips-n-Salsa - A Java library of Customizable, Hybridizable, Iterative, Parallel, Stochastic, and Self-Adaptive Local Search Algorithms
Apache AGE - Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL. [Moved to: https://github.com/apache/age]
setup-java - Set up your GitHub Actions workflow with a specific version of Java
amplify-cli - The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
cicirello - My GitHub Profile
spring-rest-crud-example - Use this repository as a basis to start the development of a new Java REST API.
gcovr - generate code coverage reports with gcc/gcov
minio-py - MinIO Client SDK for Python