Make a small piece of code to restore it on creation !

On login, add webhook scope to user repo to allow webhook generation to easy get update

main document #8

description

we need an index page to list pull requests.

technical

• it should support query parameter filters ( use a library to manage filters )
• take care of N+1

DOD

• make simple list for it
• write tests

code reviews are available at GitHub/GitLab pull requests.

somehow, on submitting the review request, we should validate whether it is a pull request.

we have some options :

• do not publish the request until a human approves it.
• use URL validation ( it has a particular schema like REPO/pull/{id} )
• use GitHub integration to get the information of a URL ( i don't know if is it possible ?) ( also is it available for GitLab and others? )

app(Endpoint)->get()

On each table add action to allow deleting from policy check

as you know, once someone creates a new review request, should mention the Github profile.

we need an integration of GitHub API to fetch more detail of User by GitHub username.

what we need to get:

• is it a valid profile?
• Avatar
• name
• bio

technical expectation

• make a service for GitHub
• after submitting the review request ( use observer on Project model ) store data on the cache
• on show and index of Project show the sample data like ( avatar and others ) with correct data ( read from cache )

as you can see on #8 we need a form for a busy man to submit their project.

then he can manage them on his dashboard:

• manage repositories
• manage pull requests ( we can do nothing for this because it's the same as making a manual review request #12 )

technical

• have a model called Repo ( do not name it Repository because conflicts naming with the Repository pattern )
• use soft delete for deletion
• do this on user dashboard.
• for now just store it and do nothing. :)
• it will be awesome if we have some test for the crud. ( simple one )

add login and register by GitHub

Running the dev app via sail can show issue on windows.
This issue is already known here : laravel/vite-plugin#28
This solution should help : laravel/vite-plugin#28 (comment)

main document #8

we should get a list of the repository pull request in certain intervals

I prefer instead of corn job, to use a timed queue, but it has its own risks.

for now

• decide update strategy
• integrate with GitHub to get the pull requests
• make a service to create pull requests.
• avoid creating duplicate pull requests.
• write strong tests please
• it will be good if find a good third party to handle GitX integrations instead of writing by hand.

so let's discuss here about the strategy.

it will be good to get the PR link from the discord.

https://spatie.be/docs/laravel-data/v3/introduction

main document: #8

description

we need detail page for pull request,
it should contain good information about the user and pull request.

technical

• for now just implement basic and wait for design in next step
• read everything from database don't do any API call to third party

In vite config load env and check https for local developpment with docker or remove all HTTPS

Build something to send message to discord

We have to create a new webhook url on the repository with the access token of the auth user and we need to be sure no ones can guess this webhook (to avoid postman push to our webhook)

Something like UUID + Crypt at the end and maybe store it into the DB ?

Webhook Model (Poly Morph ?) with UUID ?

https://docs.saloon.dev/

Codereviewpals.com is an open-source platform for code reviews. Our goal is to encourage collaboration among developers by making it easier for them to get feedback on their code. We have a blog and a section for review requests, where developers can submit their code for review by more experienced colleagues.

Goal of Landing Page

We want to create a landing page that will help us reach out to junior developers and encourage them to submit their code for review. At the same time, we want to encourage more experienced developers to review code and contribute to the community.
Sections of Landing Page

• Header: with the name of the website and a short tagline that summarizes the purpose of the website.
• Call to action: a prominent button or form that invites users to submit their code for review.
• Testimonials: a section that includes quotes from developers who have used our platform to get feedback on their code, highlighting the benefits of using the platform.
• About us: a section that provides some information about who we are, our mission, and what we do.
• Contact us: a section that includes a form or contact information for users who want to get in touch with u

Definition of Done (DOD)

• Figma design: A detailed Figma design that includes all the sections mentioned above and is aligned with the overall visual style of our website.
• Convert to HTML and CSS with Tailwind: The landing page should be responsive and compatible with different devices and browsers. It should be built with HTML and CSS using the Tailwind framework.
• Connect with Laravel: The landing page should be integrated with our Laravel application and hosted on our server.

P.s

it will be awesome if we find a UI/UX designer and frontend developer for this issue ❤️

Since we don't allow user to register and login without Github account, we don't need UiAvatar Service and code related !

Check in Github oauth first login if recently created fetch data from action

The objective behind this is to automatically delete webhook if the ping dont work (404 etc)

In every try catch block for repository, pull request about API call, maybe log somewhere all the thing with adding notification, flag or idk !

for now, we decided only to support login with GitHub ( in the future we can implement another git like GitLab. )

Create a repo on the DB when u add a pr on the website.

it's good to have some statistics

as you see #8 we need CRUD in dashboard ( just index, create, delete, edit and redirect show to an #14 )

technical

• make a model called PullRequest
• fields : title, url, status, description
• only title and url is fillable by user others will complete automaticly
• we will add more fields in future.
• use PHP enum for status and store string in database
• it will be good if we have simple feature test ( we need it in future )

Discussed in #64

we need to have a GitHub action.

the flow :

• update source code ( git pull )
• run php artisan migrate
• run npm install && npm run build
• run php artisan optimize

• insert just open and draft PRs
• check for status update (and some other data {just make structure we don't decide about which data} ) in interval

in Repo list, click on

and open repo in other tab ?

main document #8

please see #15 and #9

this website could be a hub to connect open-source contributors and project owners.

for a better experience, we should display more information about a request.

likes :

• pull request status
• project languages
• description of the pull request
• project details, stars, ...

technical

• each pull request should check status in period
• we should add more fields on PullRequest model ( based on what data we can extract )
• we should talk about update status strategy
• make a service to get detail of a pull request also check #15
• write strong test please

for Category purposes, we need to have the language main of the Pull Requests.
then we can show it better on Discord.

changes

• add language to the PR model
• create discord code review forums based on the languages
• On the website create a pull request make drop-down to specify the language
• Implement a feature for an automatic detect language
• category table ( if the possible fixe is good ) 🤷‍♂️

problems we may face:

• HTML and CSS are 2 different languages but we need them in one ( there will be more like this i think )
• we can not detect the framework, like it's Yii or Larael, React or Vue or Angular or ...
• a Pr may change a lot of files including different languages
• we may have PR to DockerFiles and we can not specify what this Pr is for

Possible fixes

• have special categories and manually and automatically make some rules to detect what the PR category is ( so we need to have a category table to add categories to the website )

Right now we only assume that github user has a real name in their profile. Because not every github user has filled out their real name, we need to also have a column for nickname.

Right now also if the user does not have a real name, sql will throw an error when such user is attempting to register because the column 'name' is not allowed to be nullable