hot VS goals-template

At OpenSauced, we make sure that each PR follows compliance checks run by a GitHub Action. This compliance action helps us to maintain the quality and organization of contributions to the repository by ensuring that pull requests follow semantic naming conventions and adhere to contribution guidelines.

After listening to the talks and tips from the space, I decided to set a 30-day target for myself to make contributions to open source projects in the month of August 2022. I got my first PR up on the 3rd of the same month https://github.com/open-sauced/hot/pull/285.

If you’re looking for an open source project to submit your first PR to, find a project that’s well documented, aligns with your interests and skills, and is accepting PRs from new contributors. Check out OpenSauced’s Hot Repositories or Insights to find popular repositories and explore based on your favorite topics. And if you want to see your PR mentioned by OpenSauced, be sure to add it to your highlights!

You can read more about PRs with @Brian Douglas’ post on Tips for getting your Pull Request reviewed on GitHub. Or check out the hottest repos and how they handle PRs on OpenSauced hot repositories. And if you have tips for creating great pull requests, let us know in the comments below.

Check out https://hot.opensauced.pizza/ for finding OSS projects to contribute to (not my site, but I have met BDougie who runs it - super great dude).

Open Source projects are a great way to show your skills, for sure. There are great tools out there for finding projects to contribute to, like OpenSauced.pizza. I've worked with some amazing devs who cut their teeth on OSS projects.

I left that as a good first issue for anyone to pick up. https://github.com/open-sauced/hot/issues/83. Links work in the list view though.

Code can be found here: https://github.com/open-sauced/hot

The last thing that I learned about with this PR was some of the effects of "sprawl" of a project. In keeping with best practices, I created an issue first before creating the PR and by the time I was finished with the PR, I noticed there was already an issue in goals-template repo. This makes plenty of sense when you think about the ways that the Open Sauced project has grown.

// https://github.com/open-sauced/goals-template/blob/main/.github/workflows/sync-2-upstream.yml name: Sync to Upstream on: schedule: - cron: '0 7 * * 1,4' # scheduled at 07:00 every Monday and Thursday workflow_dispatch: jobs: sync_with_upstream: runs-on: ubuntu-latest name: Sync HEAD with upstream latest steps: # Step 1: run a standard checkout action, provided by github - name: Checkout HEAD uses: actions/checkout@v2 with: ref: main # Step 2: run this sync action - specify the upstream repo, upstream branch to sync with, and target sync branch - name: Pull upstream changes id: sync uses: bdougie/Fork-Sync-With-Upstream-action@fork with: upstream_repository: open-sauced/goals-template upstream_branch: main target_branch: main # optional github_token: ${{ secrets.GITHUB_TOKEN }} # optional, for accessing repos that require authentication # Step 3: Print a helpful timestamp for your records (optional) - name: Timestamp run: date