Code Monkey home page Code Monkey logo

ai'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

ai's People

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  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  avatar  avatar

ai's Issues

Add to (OpenSauced) insight repo button

Today when a user is exploring they can add a project to an insights page on OpenSauced. I would love a feature when they can add a repo to a page while browsing GitHub.

My thought is adding a dropdown to a voting button. Similar to the star list dropdown.

Uploading Screen Shot 2023-04-18 at 5.59.44 AM.pngโ€ฆ

Screen Shot 2023-04-18 at 5 57 49 AM

Feature: New data on highlights page.

Type of feature

๐Ÿ• Feature

Current behavior

Instead listing open issues, which is not useful, list highlights counts.

https://api.opensauced.pizza/#/User%20Highlights%20service/addHighlightForUser

Screen Shot 2023-05-13 at 8 15 18 AM

Suggested solution

  1. Replace issues with total highlights
  2. Change total PRs to PRs (currently) opened

Change this line
https://github.com/open-sauced/browser-extensions/blob/d49015d9e9abc8500f9ca7e7b21720b5c764032a/src/pages/profile.tsx#L153

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: Chrome extension

Type of feature

Select the type of feature request, the lowercase should also be the PR prefix.

  • ๐Ÿ• Feature
  • ๐Ÿ› Bug Fix
  • ๐Ÿ“ Documentation Update
  • ๐ŸŽจ Style
  • ๐Ÿง‘โ€๐Ÿ’ป Code Refactor
  • ๐Ÿ”ฅ Performance Improvements
  • โœ… Test
  • ๐Ÿค– Build
  • ๐Ÿ” CI
  • ๐Ÿ“ฆ Chore (Release)
  • โฉ Revert

Current behavior

I can provide more context, but the focus would be injecting features into the GitHub repo page.

Suggested solution

Describe the solution you'd like.

  • recommend assignees to issues or PRs
  • Display stats
  • add repo to indexing queue (hot submissions)

Code of Conduct

By submitting this issue, you agree to follow our Code of Conduct.

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

Contributing Docs

If you plan on contributing code please read - Contribution Guide

  • I agree to follow this project's Contribution Docs

Bug: odd location of view on open sauced

Describe the bug

The location of view profile on open sacued is okay on other pages, but it's odd on personal page here is a screenshot

view of open sauced location

Suggestions:

Add a control to check if it's the personal page to add it on the right location,

Steps to reproduce

  1. open your own profile page.

Affected services

browser-extension

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: invite non members to opensauced

Type of feature

๐Ÿ• Feature

Current behavior

Opened an issue in the flagship project to check on member status. Notice we are also not checking for that here and need to add.

open-sauced/app#1124

Suggested solution

Add is_opensauced_member check to the 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: Emojify user profile description

Type of feature

๐Ÿ• Feature

Current behavior

First of all, thanks so much for the great work you have been putting into this project ๐Ÿ• The extension looks really great ๐Ÿ”ฅ

Currently, emojis are not rendered correctly. see

opensauced-extension-edit

Suggested solution

Use the same or similar lib used in open-sauced/hot#449 to render emojis

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: List the latest Highlights

Type of feature

๐Ÿ• Feature

Current behavior

Open to different design, but let's add latest highlights to the drodown.

Group 4

Suggested solution

  1. List the latest highlight, and provide the ability to react to the highlight.
  2. It would be nice to paginate to the next highlight.
  3. While on a repo, if a highlight exist for that repo, it should filter to only show that repo's highlights.

Additional context

The open-sauced/insights repo will have implementation for filtering highlights

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: Incorporate Linkedin features

Type of feature

๐Ÿ• Feature

Current behavior

This extension should include linkedin data

Suggested solution

Features

  1. Update projects on LinkedIn project
  2. Including ability to modify LinkedIn
  3. List previous experience in the dropdown.

Screen Shot 2023-05-01 at 6 51 58 AM

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: Browser Extension

(Copy of #3)

Type of feature

๐Ÿ• Feature

Current behavior

We aren't getting submissions on the platform

Suggested solution

make an extension that suggests submissions for opensauced when user stars a repo.

Would love ideas on this approach.

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: Generate pull request descriptions with AI

Type of feature

๐Ÿ• Feature

Current behavior

I know github has shipped this in private beta and WTD also has a paid version.

Suggested solution

similar to #12. Button on the PR to generate the description.

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: Update chrome extension logo to opensauced logo

Type of feature

๐Ÿ• Feature

Current behavior

Screen Shot 2023-04-18 at 6 11 46 AM

Suggested solution

Should use the plain icon, no gradient or border (I don't have an example, icon is on the press page).

Screen Shot 2023-04-18 at 6 14 58 AM

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: Try/Catch mechanisim

Type of feature

๐Ÿ• Feature

Current behavior

The fetch API has no try/catch mechanism right now to check the errors from the server side, I think it would be great to have such a thing.

An example from the insights project: https://github.com/open-sauced/insights/blob/beta/lib/hooks/createHighlights.ts#L18

Suggested solution

No response

Additional context

It would be great to have such a thing to debug and understand errors when it happens.

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: Extending AI to comments

Type of feature

๐Ÿ• Feature

Current behavior

Right now the AI feature only working on the PRs it would be great to have it on the comments as well or use it a user prompt for it.

Suggested solution

I am taking grammarly extension as example, when you write a text Grammarly allows you to select the text and enhance it.
You can see the image for their UI:
image
and here is the options that it shows when you select the text:
image

As for open sauced, I feel like we can have something similar that we can use for comments. The user would write a short comment and we can enhance it or even review conversation and write a comment based on the user prompt.

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: Username text alignment is off

Describe the bug

When the username is too short.

Expected Behaviour:
image
Current Behaviour:
image

Steps to reproduce

  1. Login
  2. Click on your profile
  3. Look at the username

Affected services

browser-extension

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: Add linting to the project.

Type of feature

๐Ÿ• Feature

Current behavior

Since the src has now grown to a considerable size , it might be appropriate to enforce a code standard and styling.

Suggested solution

Adding linting to the project using ESLint. We can base our linting rules on the existing rules used in other OpenSauced repositories to maintain uniformity across projects.

Additional context

Original suggestion here: #20 (comment)

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: Build error - top level await

Describe the bug

vite v2.9.15 building for production...
โœ“ 51 modules transformed.
rendering chunks (2)...[vite:esbuild-transpile] Transform failed with 1 error:
assets/profileScreen.ts.af6d3823.js:167:25: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2019", "firefox78", "safari13.1")

Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2019", "firefox78", "safari13.1")
165|  const username = getGithubUsername(window.location.href);
166|  if (username != null) {
167|    const openSaucedUser = await getOpenSaucedUser(username);
   |                           ^
168|    if (openSaucedUser)
169|      injectViewOnOpenSaucedButton(username);

error during build:
Error: Transform failed with 1 error:
assets/profileScreen.ts.af6d3823.js:167:25: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2019", "firefox78", "safari13.1")
    at failureErrorWithLog (/Users/bdougie/code/browser-extensions/node_modules/esbuild/lib/main.js:1624:15)
    at /Users/bdougie/code/browser-extensions/node_modules/esbuild/lib/main.js:1413:29
    at /Users/bdougie/code/browser-extensions/node_modules/esbuild/lib/main.js:678:9
    at handleIncomingPacket (/Users/bdougie/code/browser-extensions/node_modules/esbuild/lib/main.js:775:9)
    at Socket.readFromStdout (/Users/bdougie/code/browser-extensions/node_modules/esbuild/lib/main.js:644:7)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

Steps to reproduce

A new build error was introduced in the last merge.

Affected services

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: How we do releases documentation

Type of feature

๐Ÿ• Feature

Current behavior

@diivi I merged your PR, but noticed that the source code is upload and the not dist folder.

Regardless, I wanted to see if we could add documentation to this readme on how we do releases.

  • The beta branch is default
  • We squash & merge to beta branch PRs
  • We never commit directly to main

Suggested solution

Copy in the README for now, but we will want to add this to docs.opensauced.pizza too.

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: 5 feature screenshots

Type of feature

๐Ÿ• Feature

Current behavior

Need 5 screenshots for the chrome store

Suggested solution

  1. profile data
  2. highlights in actions
  3. invite others to open sauced
  4. view profiles
  5. upvoting

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: multiple open sauced icons

Describe the bug

This happens when I navigate between PRs.

image

Steps to reproduce

  1. go to: https://github.com/open-sauced/insights/compare/beta...a0m0rajab:insights:update-readme-test?expand=1
  2. you will see the open sauced icon
  3. go to issues by clicking on it
  4. return to the first page in step 1 with return button
  5. you will see the icon being added.

video:

www_screencapture_com_2023-5-18_17_55.mp4

Affected services

browser-extension

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: auth'd dropdown

Type of feature

๐Ÿ• Feature

Current behavior

Thanks to #27, when a user authenticates they are presented with a dropdown page. We should provide some context here.

Screen Shot 2023-04-22 at 7 10 52 AM

Suggested solution

Create a page for auth'd users that allows the following.

  1. Create highlight button for that contribution.
  2. See more summary of details about currently viewed profile.

@doaortu you had a great version of this in your submission. Any interest in contributing?

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: Chrome extension tracking

Type of feature

๐Ÿ• Feature

Current behavior

Today we will begin work on the OpenSauced Chrome extension. The initial version should have a button for OpenSauced users only.

Goal:

Drive engagement to OpenSauced.

Key Responsibilities:

  • Building features for the browser extension
  • Building reusable UI components referencing our existing design system
  • Building interactions to communicate with GitHub and our API
  • Participate in design and engineering reviews to provide feedback during team meetings
  • Monitor application performance
  • Provide solutions to various solutions based on complexity and tradeoffs.

Suggested solution

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: Update manifest version after release

Type of feature

๐Ÿ• Feature

Current behavior

When a release is made, the tag is created and the package package.json version is bump using open-sauced/release. The manifest file is not updated during this process.

https://github.com/open-sauced/browser-extensions/blob/beta/manifest.json#L4

Suggested solution

Create a script in this repo that bumps the version. This does not need to be added to the open-sauced/release project since this is specific to the browser extension.

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: Add support for conventional commits

Type of feature

๐Ÿ• Feature

Current behavior

PR Validation

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: Chrome extension

Type of feature

๐Ÿ• Feature

Current behavior

We aren't getting submissions on the platform

Suggested solution

make an extension that suggests submissions for opensauced when user stars a repo.

Would love ideas on this approach.

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: Service worker to check user in the background

Type of feature

๐Ÿ• Feature

Current behavior

When viewing a profile the browser extension does register or add a button right away. I need to refresh the page for it to work sometimes.

shamim.mp4

Suggested solution

This is pretty common on !user.is_opensauced_member.

My guess is have the service worker start checking as soon as the page is requested.

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: Clicking on users image should take you to opensauced

Type of feature

๐Ÿ• Feature

Current behavior

Screen Shot 2023-05-01 at 6 54 56 AM

Suggested solution

Click the profile and send the user to their opensauced profile.

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: add PR to highlights from the extension

Type of feature

๐Ÿ• Feature

Current behavior

it would be gerat to have an auto add option for PRs/issues to the extension where it will be not let the user move to the highlight page, or at least open highlight page with the PR information loaded (as first step)

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

Improve README

  • Needs setup instructions
  • Needs the goal and focus for the project
  • List the core team

Feature: Integrate allcontributors into the extension

Type of feature

๐Ÿ• Feature

Current behavior

https://allcontributors.org/

Suggested solution

Getting insights into contributors on a project would be ideal. Probably last commit or link top3 contributors.

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: Link the users to open-sauced/feedback/discussions for feedback

Type of feature

๐Ÿ• Feature

Current behavior

Users do not have a place to report ideas and feedback on the extension. They need a link to https://github.com/orgs/open-sauced/discussions

Suggested solution

Link in the docs.opensauced.pizza and the extension window.

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: CI deprecations

Type of feature

๐Ÿ• Feature

Current behavior

https://github.com/open-sauced/browser-extensions/actions/runs/4821813888

Screen Shot 2023-04-27 at 8 52 46 AM

Suggested solution

Set environment variables
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

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: Generate descriptions for larger PR & releases

Type of feature

๐Ÿ• Feature

Current behavior

Release PRs will always be too large for the PR Ai description generator. https://github.com/open-sauced/browser-extensions#-releases

Instead of AI, we should use the same logic to generate release notes.

examples of a release: https://github.com/open-sauced/browser-extensions/releases/tag/v1.1.0-beta.2

Suggested solution

List out commits marked as conventional commits. We can use the logic from open-sauced/release.

This is powered by semantic release.

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: Button should also work in light mode.

Describe the bug

Screen Shot 2023-04-19 at 6 32 35 PM

Steps to reproduce

Turn on light mode and navigate to https://github.com/Anush008

Affected services

pizzaface

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: Add good first issues to the dropdown for the repo

Type of feature

๐Ÿ• Feature

Current behavior

TBD

Suggested solution

TBD

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: change in size GitHub (UX)

Describe the bug

When you open GitHub with the extension enabled it resizes the screen and change dimension which is a bit uncomfortable.

Steps to reproduce

  1. enable the extension.
  2. go to: #88
  3. you see a minor resize at the beginning, (you might need to force refresh to see the issue (CTRL+SHIFT+R))
  4. disable the extension
  5. go to link in step 2
  6. you see there is no resize
www_screencapture_com_2023-5-18_18_12.mp4

Affected services

browser-extension

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: Remove dependency on user provide openai tokens

Type of feature

๐Ÿ• Feature

Current behavior

Screen Shot 2023-05-18 at 3 58 22 AM

Storing the OpenAI token creates a hurdle for the user, and we will need to remove it.

Suggested solution

OpenSauced will provide a token and no longer require the user to enter their token

Leverage the endpoint here: open-sauced/api#167.

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

Developer Documentation to onboard interested contributors.

Type of feature

๐Ÿ“ Documentation

Current behavior

Currently, jumping in and contributing to the codebase seems a bit difficult, considering all the design decisions we have taken are not documented, and even I need to refer to past components to add new ones.

This adds friction and makes onboarding new devs difficult.

Suggested solution

I suggest adding a CONTRIBUTING.md with all the design decisions that we've taken; it should convey the following (at least):

  1. How to manipulate the GitHub website to add custom components. (the whole dom-utils -> components etc flow)
  2. How to edit/add features to the extension popup.

Adding new features is good, but we should probably leave issues like #59 and #66 open for new contributors and add some docs for our decisions.

This is more of a documentation tracker than a single issue:

  • Add DOM manipulation docs
  • Add extension popup editing docs
  • How do we do authentication?
  • How is state managed

etc.

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: AI code refactoring

Type of feature

๐Ÿ• Feature

Current behavior

With #79 winding down and getting ready for completion, thinking of the next AI feature ideas.

feel free to discuss other ideas in the discord

My pitch is to use the inline comment on the file changes to generate suggested changes

Suggested solution

A user can use suggested changes to generate new code using the [suggested changes feature]

The example below is me pointing at the "suggested changes" button. I am suggesting an enum instead of a case statement and using the AI to generate the enum.

(https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) and OpenSauced.ai
Group 5 (1)

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: Limit permissions for the extension to GitHub

Type of feature

๐Ÿ• Feature

Current behavior

Screen Shot 2023-05-22 at 5 18 32 PM

Suggested solution

By default these settings is marked for "all sites"

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: Presenting button when no bio present

Hey @bdougie. Upon investigation, I discovered that GitHub adds a "hidden" attribute to the bio-div of profile pages in case no bio is present, which was the case in https://github.com/dayhaysoos. This attribute affects the visibility of the "View On OpenSauced" button located as a child to the bio-div and causes it to remain hidden from view. I'll try to to update how the "View On OpenSauced" button gets added onto the page.
hidden-bio

Originally posted by @Anush008 in #20 (comment)

Bug: Duplicate buttons when switching tabs on a user's profile

Describe the bug

image

When switching from the overview to the repositories tab, a duplicate "View on OpenSauced" Button gets added to the webpage.

Steps to reproduce

  1. Go to a profile
  2. Click on repositories

Affected services

browser-extension

Platforms

Desktop

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 PR to OpenSauced Highlights button

Similar interaction to the Gif for GitHub extension - Look at the end of the this post for context

Screen Shot 2023-04-17 at 6 51 13 AM

Proposed solution

Add a OpenSauced icon to the GitHub PR markdown editor. Generate copy based on commits and in the case of issue comments, generate a response to the comment.

This would be our first AI exploration @0-vortex, would love your thoughts.

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.