Giter VIP home page Giter VIP logo

.github's Introduction

This repo is archived. If you are looking for the latest, check out open-sauced/insights or open-sauced/hot.


Open Sauced

πŸ• Open Sauced πŸ•

The path to your next Open Source contribution

CodeQL Compliance Release Publish stories if changed Netlify Status Dependabot Badge GitHub code size in bytes GitHub commit activity GitHub issues GitHub Release Discord Twitter

Open Sauced provides structured onboarding for new contributors to open source. This structure provides a way to track your next contributions by leveraging a unique dashboard built on top of the GitHub GraphQL API.

open-sauced-screencap

πŸ“– Prerequisites

In order to run the project from a container we need node>=14, npm>=7 and docker>=20 installed on our development machines or use one of the listed cloud providers we support:

Gitpod

βœ… fully ready integrated development environment

β­• VS Code settings sync is not ideal

Open in Gitpod

Gitpod is mostly free but has extensive documentation for all its contributing features.

For Vite to work with Gitpod we need to use a custom Dockerfile that lives under .gitpod.Dockerfile.

Open Sauced comes with a pre-defined .gitpod.yml that should work out of the box in multiple contribution scenarios.

Replit

βœ… fully ready integrated development environment

β­• modified contribution workflows

Open in Replit

Replit is an old service that recently supported NixOS, enabling full customisation of the runner and project.

Open Sauced is configured with a shell environment supporting node@16 and npm@8. The build environment script lives in shell.nix and the repl config lives in .replit.

Codesandbox

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• low resources free tier limitations

Open in CodeSandbox

Stackblitz

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• limited documentation on container limitations

Open in Stackblitz

Glitch

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• does not support stacked hot module reload

β­• severely low resources free tier limitations

Remix on Glitch

πŸ–₯️ Local development

To install the application:

npm ci

To start a local copy of the app on port 3000:

npm start

πŸ§ͺ Test

For running the test suite, use the following command. Since the tests run in watch mode by default, some users may encounter errors about too many files being open. In this case, it may be beneficial to install watchman.

npm test

You can request a coverage report by running the following command:

npm run test:coverage

πŸ“¦ Docker builds

A development preview can also be run from docker:

docker build -t open-sauced-dev .
docker run -p 8080:80 open-sauced-dev

Alternatively you can pull the production container and skip all builds:

docker run -dit -p 8080:80 ghcr.io/open-sauced/open-sauced

🎨 Code linting

To check the code and styles quality, use the following command:

npm run lint

This will also display during development, but not break on errors.

To fix the linting errors, use the following command:

npm run format

πŸš€ Production deployment

A production deployment is a complete build of the project, including the build of the static assets.

npm run build

You can analyze the build by running the following command:

npm run build:analyze

🎭 Offline asset optimization

We also have a script for updating .svg files used in the project, you only need to run this if you add new assets:

npm run build:svgo

And one for .png and .jpg files:

npm run build:squoosh

🚧 Development debugging

Thanks to antfu/vite-plugin-inspect we can always inspect the bundles in development by navigating to localhost:3000/__inspect/ in your browser.

πŸ“™ Storybook

Storybook is being leveraged to mock out visual React components. The latest version of the design system can be found at this URL.

npm run storybook

storybook example screenshot

πŸ”‘ Authentication

Authentication is handled through OneGraph's AuthGuardian service.

πŸ’Ύ Database

This project uses GitHub as a database. When you login, you will be presented with a button to create a goals repository. That repository template lives at open-sauced/goals-template.

πŸ’¨ Service Worker

This project uses the sw-precache to kickstart an offline cache. The offline cache only registers in production. If service needs to be manually removed make an unregister call from the registerServiceWorker.js import.

πŸŒ™ Dark Mode

This project supports "dark mode" styling, and by default it will follow the color preference on your device. It also allows for overriding this using buttons at the top right of the screen, which will persist the preference to local storage on your device. More info about color preference web API's can be found here: MDN Web Docs

πŸ“ Markdown Support

This project leverages Remirror for a delightful experience in documenting your Open Source goals. The editor supports markdown features including heading levels, bulleted lists, text formatting, code snippets, and emojis!

🀝 Contributing

We encourage you to contribute to Open Sauced! Please check out the Contributing guide for guidelines about how to proceed.

We have a commit utility called @open-sauced/conventional-commit that helps you write your commits in a way that is easy to understand and process by others.

It is generally integrated as an npm script but you can run it with npx as well:

npm run push

For any other npm based project or dotnpmrc defaulting to --yes:

npx -y @open-sauced/conventional-commit

πŸ• Community

Got Questions? Join the conversation in our Discord.
Find Open Sauced videos and release overviews on our YouTube Channel.

🎦 Repository Visualization

Visualization of this repository

βš–οΈ LICENSE

MIT Β© Open Sauced

.github's People

Contributors

0-vortex avatar a0m0rajab avatar adiati98 avatar arielmaj avatar bdougie avatar bekahhw avatar dhananjay-jsr avatar sadiejay avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

.github's Issues

Feature[DOCS]: Add Gitpod and CodeSpaces link to Contributing file

Type of feature

πŸ• Feature

Current behavior

In my experience working with open source beginners, sometimes the directions to setting up a code environment do not always pan out, which creates a frustrating experience. Furthermore, some might not be able to afford their own computer and can only use virtual IDEs.

Suggested solution

Adding links to CodeSpaces and Gitpod to the Contributing file can make it easier for open source beginners to get started.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

GitLab Authentication

Type of feature

πŸ• Feature

Current behavior

At the moment, OpenSauced seems to be only available for GitHub. As someone who’s making contributions to other open source projects on GitLab, this can make it difficult for me to showcase my merged MRs.

Suggested solution

Somehow create a pathway where users can login with GitHub and GitLab

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: upgrade issue templates to yaml syntax forms

Is your feature request related to a problem? Please describe.

There is no πŸ• without the latest and greatest feature from GitHub: yaml syntax forms

Describe the solution you'd like

Implement yaml syntax forms

Describe alternatives you've considered

Making users click boring checkboxes and having to delete and/or adjust the issue template also involves a lot of reading. It's 2022, people suddenly enjoy filling out forms ...

Additional context

Bug: incomplete platforms for bug report

Describe the bug

When opening a new ticket, a user is unable to select non-frontends from the list of platforms, browsers, and environments.

Steps to reproduce

  1. Open a new issue
  2. In platforms select "other" or "none"

Affected services

opensauced.pizza, admin.opensauced.pizza, docs.opensauced.pizza, explore.opensauced.pizza, semantic-release-conventional-config, pizzaface, slaybot, beybot

Platforms

Desktop

Browsers

Other (add additional context)

Environment

Production

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Feature: add contributing docs to the issue agreement

Type of feature

πŸ• Feature

Current behavior

When opening an issue we are tasked to read the contributing covenant, for the people that open issues in order to .take them, it is important to optionally add the contributing docs to the terms.

Suggested solution

Add https://docs.opensauced.pizza/contributing/introduction-to-contributing/ next to the code of conduct link in all templates, make it optional.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Bug: Typo in Pull Request Template

Describe the bug

In the PULL_REQUEST_TEMPLATE.md the last comment line reads:

note: PRs with deletes sections will be marked invalid




I believe the intended statement is either:

note: PRs with deleted sections will be marked invalid

or

note: PRs which deletes sections will be marked invalid

Steps to reproduce

Open a PR for an Open Sauce project and the template will appear via github actions.

Affected services

opensauced.pizza, hot.opensauced.pizza, api.opensauced.pizza, docs.opensauced.pizza, explore.opensauced.pizza

Platforms

Desktop, Mobile, Tablet

Browsers

Chrome, Firefox, Safari, Edge, Opera, Other (add additional context)

Environment

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: Placeholder text on wrong field

Describe the bug

In the bug report form, the placeholder text appears to be meant for the β€œSteps to Reproduce” rather than the Bug Description.
D36F0EFA-2295-4C9E-96AF-E849777B1800

Steps to reproduce

  • Start to file an issue bug report
  • Get excited that you might get to file an issue with a GitHub beta feature
  • Realize there’s a bug in the bug report form

Affected services

opensauced.pizza, admin.opensauced.pizza, docs.opensauced.pizza, explore.opensauced.pizza

Platforms

Desktop, Mobile

Browsers

Chrome, Firefox, Safari, Edge, Opera

Environment

Production

Additional context

This is so meta

Code of Conduct

  • I agree to follow this project's Code of Conduct

Feature: explore pinned repositories customisations

Type of feature

CI

Current behavior

we are manually pinning the repositories displayed on the @open-sauced org

Desired solution

explore the possibility of reordering the pinned repositories based on activity and stars and put it in a cron workflow

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Add an editing the page

Type of feature

πŸ• Feature

Current behavior

I noticed that the repository is missing edit this page buttons.

Suggested solution

I think we should add one. To stay consistent with the other repos.

Edit the page screenshot

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: improve issue templates

Type of feature

Refactor

Current behavior

our issue templates are designed for React frontend applications

Desired solution

  • adjust the yaml syntax forms to distinguish between node server, client and server-less functions
  • correct the logical relationships between Bug and our questions
  • make the forms more compact, if possible

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Feature: request images in the bug report

Type of feature

πŸ• Feature

Current behavior

when you have a bug report it would be great to have images from the user and screen capture this would make it easier to understand their logic and story to get a solution for that.

Suggested solution

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Maintaining your own project

Type of feature

πŸ• Feature

Current behavior

Open source members need to learn how to start working on their own open source projects.

Suggested solution

A course or section on this topic. It would come after what I suggest in issue #26. Basically a scaffolding approach.

Additional context

I'm willing to co-develop this feature

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Change twitter icon X

Describe the bug

Replacing The Twitter icon in the footer section to its new icon

Steps to reproduce

.

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: open-sauced repo without a open source license

Describe the bug

There's no open source license, so I really feel like I can't use what's available here.

Steps to reproduce

  1. Go to repository;
  2. See that there's no open source license;
  3. Cries because the PR/Issue templates are beautiful but you can't use them.

Browsers

Chrome, Firefox, Safari, Edge, Opera

Additional context (Is this in dev or production?)

Production

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: add test steps to the PR template

Type of feature

πŸ• Feature

Current behavior

it would be great to add a QA test steps for the PR template to help people to see how is the normal behavior's should be.

Suggested solution

NA

Additional context

Na

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: Bug issue template is absence when creating an issue

Type of feature

πŸ› Fix

Current behavior

Recently, there was an update to the bug_report.yml which caused an error and the absence of bug issue template as shown in the screenshots below.

Note: I'm using the feature issue template to submit this bug.

YAML Syntax Error

Screenshot 2024-03-24 041044

Absence of bug issue template on app repo.

Screenshot 2024-03-24 040740

Suggested solution

This bug is most likely caused by incorrect indentantion. Fixing the indentation may resolve this.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: rename @open-sauced/semantic-release-conventional-config

Describe the bug

it's https://github.com/open-sauced/release now

Steps to reproduce

both actions are usable but https://github.com/open-sauced/semantic-release-conventional-config is behind release

Affected services

opensauced.pizza, hot.opensauced.pizza, docs.opensauced.pizza, explore.opensauced.pizza, semantic-release-conventional-config

Platforms

No response

Browsers

No response

Environment

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: contributors profile local time is not accurately representing the minutes in `tens`

Describe the bug

The minute in users local time is not properly formatted when in units
Screenshot_20230618-110920_Chrome

It should be 11:08am instead

Steps to reproduce

Visit a profile when thier local time minute is not up to tens

Browsers

Chrome

Additional context (Is this in dev or production?)

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: add open-sauced/hot to templates

Describe the bug

hot.opensauced.pizza is missing from the bug and feature templates

Steps to reproduce

Go to any open-sauced/* repository and file a new bug, affected services are missing hot

Affected services

opensauced.pizza

Platforms

Desktop

Browsers

No response

Environment

Production

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

feat: improve first-time contributor message in greeting yml file

Type of feature

πŸ• Feature

Current behavior

I noticed that the message for first-time contributors is not personalized enough, which can make the experience a bit assembly-line-like.

Suggested solution

Instead of:
PR_COMMENT="Congratulations on completing Chapter 5 of the Intro to OSS Course with your contribution to this repository! You're almost to the end of the course. Create a highlight of your contribution to our guestbook using the instructions in chapter 6 and share it with us!"
curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" -X POST -d "{"body":"$PR_COMMENT"}" "https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments”

How about:
PR_COMMENT="Congratulations on completing Chapter 5 of the Intro to OSS Course with your contribution to this repository @${{ github.actor }}! You're almost to the end of the course. Create a highlight of your contribution to our guestbook using the instructions in chapter 6 and share it with us!"
curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" -X POST -d "{"body":"$PR_COMMENT"}" "https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments"

It'll make the contributor feel more welcomed.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: Error on `/user/[username]` route on some Mobile browsers

Describe the bug

On Visit to user/[username] route specifically on the Brave Browser Mobile, the error below occurs.

Screenshot_2023-08-05-16-56-06-909_com brave browser

This has been the case for as long as I've been in the community, 1.5month+ now.

It work alright on Chrome Mobile browsers I have since tested on other browser I can reach on my mobile and here' are the results

  • Chrome βšͺ Mobile - Works βœ…
  • Opera πŸ…ΎοΈ Mini - Application Error ❌
  • Brave 🦁 Mobile - Application Error ❌
  • Kiwi πŸ₯ Browser - Application Error ❌

Steps to reproduce

On the browsers stated as ones with error.

  1. Visit the highlights page at /feed
  2. Click on any user profile which should route you to /user/[username]

Expected Behaviour

The User Profile should be opened normally

Actual Behaviour

The page opens to an error message Application error: a client-side exception has occurred (see the browser console for more information).

Browsers

Opera, Other (add additional context)

Additional context (Is this in dev or production?)

Brave Mobile, Kiwi, Opera Mini

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Dev card isn’t loading

Describe the bug

When I try to access my dev card, I get an error.
IMG_3683

Steps to reproduce

  1. Go to https://insights.opensauced.pizza/user/BekahHW
  2. see error

Browsers

Safari

Additional context (Is this in dev or production?)

Prod. I’m currently on mobile using the 5g network.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: rename "opensauced.pizza" to "app.opensauced.pizza" in bug report template

Type of feature

πŸ› Fix

Current behavior

image
Currently, the option "opensauced.pizza" refers to app.opensauced.pizza project but has an outdated name, since now all open sauced projects have "opensauced.pizza" in their names, but differ in the first section of it, like "hot" or "api". This is in bug report template.

Suggested solution

So to be more clear on what we mean with "opensauced.pizza" and to be up to date with the new naming conventions, it should be updated to "app.opensauced.pizza".

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

LI Image doesn’t render

Describe the bug

When you share the card to LinkedIn from desktop, the image is broken.

27AE0F2A-6856-494D-9B21-9DDD51BDE513

Steps to reproduce

  • Click on share this card
  • Share to LinkedIn
  • See no image ☹️

Affected services

insights.opensauced.pizza

Platforms

No response

Browsers

No response

Environment

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: track latest stargazers

Type of feature

CI

Current behavior

we are not displaying any stargazers, like @bdougie does

Desired solution

explore the possibility of displaying latest stargazers across all our repos and updating that content via a new workflow

Additional context

https://github.com/bdougie

Code of Conduct

  • I agree to follow this project's Code of Conduct

Intro to becoming a maintainer

Type of feature

πŸ• Feature

Current behavior

As fairly new open source maintainer, I have not seen as much content on getting to that role(note: in this context, maintainer refers to maintaining another person’s project) in comparison to becoming a contributor.

Suggested solution

I highly recommend course or a section on how people can transition from contributing to other people’s projects to helping maintain them.

Additional context

I'm willing to co-develop this feature

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: responsiveness

Describe the bug

List in the navbar ain't 100% mobile responsive.
Screenshot_20220816-035929

Steps to reproduce

  • The fontsize can be reduced
  • list can be displayed as block item

Affected services

hot.opensauced.pizza

Platforms

Mobile

Browsers

Chrome

Environment

Production

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Add a note about picking the right issue template in Step 1 of β€œLet's Get Practical”

Type of feature

πŸ• Feature

Current behavior

One of the community members on Discord commented on how they were unsure which issue template to pick while reading step 1 in the Let’s Get Practical section

https://github.com/open-sauced/intro/blob/c3c863688ef04649a2190332db97250867f03137/05-how-to-contribute-to-open-source.md?plain=1#L142

Suggested solution

  1. Go to Step 1 in the Let's Get Practical section
    https://github.com/open-sauced/intro/blob/c3c863688ef04649a2190332db97250867f03137/05-how-to-contribute-to-open-source.md?plain=1#L142
  2. Make the following change

1. Create an issue by clicking the "New issue" button in the "Issues" tab, picking the template that best suits the contribution, and completing the form.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.