semantic-release-conventional-config
docs
semantic-release-conventional-config | docs | |
---|---|---|
3 | 5 | |
5 | 67 | |
- | - | |
7.0 | 9.0 | |
about 2 years ago | 12 days ago | |
JavaScript | JavaScript | |
MIT License | 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.
semantic-release-conventional-config
-
Generate PDF handbook with Docusaurus using GitHub Actions
open-sauced/semantic-release-conventional-config@v3 - semantic-release configuration, docker container and GitHub action
-
Semantic release to npm and/or ghcr without any tooling
Release to npm from ghcr container:
-
Automatically update git major tags on GitHub marketplace release
Having previously dockerized our semantic release configuration in @open-sauced/semantic-release-conventional-config, a manual step was needed to publish the action in the GitHub marketplace.
docs
-
Job Seekers Worksheet: Build Your Resume with Open Source
Feel free to share and adapt this worksheet. We super stoked that @codergirl1991 is working on an issue for how to use OpenSauced for job seekers. So if there's more you'd like to see, let us know!
-
What to do when your PR fails
Yesterday, I decided to make some "quick" changes to the OpenSauced docs site. Now, I know that "quick changes" is essentially a bad word in tech. Anytime you say it, it will indeed not be quick. I wrote up a quick issue that described reorganizing a couple of things and adding a quick intro page. I made the changes, wrote the page, pushed my changes, and made the Pull Request (PR), only to see that I failed. Ugh. It was quick, but it wasn't right. Not really having the time to dig into it, I left my PR open and determined to get back to it the next day. Understanding why a project is failing may look different depending on how it is set up. For us, we're going to look at implementation errors, compliance issues, check the deploy log.
-
Strategies for Successful Contributor Onboarding
At OpenSauced, we’ve been working to curate a contributor journey that allows for contributors to grow. We have repositories made for new contributors, like our Intro Course, pizza-verse, and guestbook. We also include good first issue labels on some of the issues in our app, which is generally geared towards someone leaving the new stage and entering the intermediate stage. In the same way, our docs repo has a variety of issues open to different levels. And finally, there’s always space for our expert contributors across the repositories.
-
Generate PDF handbook with Docusaurus using GitHub Actions
Yaml file link: @open-sauced/docs.opensauced.pizza/main/.github/workflows/release.yml
-
How to lint PRs and welcome contributors using GitHub Actions
The full workflow is available here: .github/workflows/compliance.yml
What are some alternatives?
docusaurus-prince-pdf - Docusaurus PDF generator using Prince XML
conventional-commit - commit binary powered by commitizen with conventional commit standard
setup-node - Set up your GitHub Actions workflow with a specific version of node.js
open-sauced - 🍕 This is a project to identify your next open source contribution.
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
first-interaction - An action for filtering pull requests and issues from first-time contributors
npm-install - GitHub Action for install npm dependencies with caching without any configuration
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed
docs.opensauced.pizzaLICENSE
exec - :shell: semantic-release plugin to execute custom shell commands
actions-gh-pages - GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.