Official repository for Find A PR. Find A PR is a platform that curates a list of issues around Laravel based project.

Closes issue: #102

cc @jaetoole

This PR adds a model, console command and a job to tweet new issues.

The console command is schedules after the repos:load command. It fetches the cached issues. Using the SocialPost model, it filters out issues that have already been tweeted. Then it dispatches jobs to tweet un-tweeted issues.

Successful tweet sent from the project: https://twitter.com/myth5407/status/1554906577555030025

Creating this as a draft, as I would like to add some tests. Early feedback is appreciated, though!

Now that the site has support for being used on a mobile, I think it'd be really cool to take it a step further and add PWA functionality.

This could allow users to add the site as a PWA to their phones and PCs so that they can quickly jump in and check for open issues.

Of course, this isn't going to serve a huge amount of purpose, but could be a pretty good chance to experiment with some cool features.

After your comment, I did some testing and didn't notice a big performance decrease. With chunking, there could also be the problem of a failing job that then doesn't fetch new issues for the other repos that were in the collection.

I am a beginner and haven't used sail before. Then I saw that there were two commands that were missing from a beginner's point of view. That's why I have added two points there So that, a beginner can understand the complete roadmap.

Interesting project! I had the same idea but not for specific technology. I wanted to make it based on type of issues. I think both can be combined!

Anyway, I wanted to ask about license of this project. There is no license in the repo. The license section in the README also talks about Laravel license. May you please make it clear that if this project is a Free/Libre and Open Source software?

Thanks

This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.

Before merging, you need to:

• Checkout the shift-66562 branch
• Run composer update
• Run npm install
• Review all comments for additional changes
• Thoroughly test your application (no tests?, no CI?)

Please send your feedback to [email protected] or share the good vibes on Twitter.

With #77 merged we can now ignore issues without getting a warning. On mobile there is currently no way of viewing the ignored issues. This PR adds an option to show the sidebar so ignored issues can be shown and un-ignored.

There are some archived repos in config/repos.php, I think it would be good if they are ignored when crawling. They also should be hidden in the sidebar.

When an error is thrown, the logger tries to log the error to bugsnag. Most of the developers don't have this set up, so another error is shown. This can cause some confusion.

This PR fixes that by setting the LOG_CHANNEL in the .env.example to single.

When I install findapr, I got 503 error. I think that comes from bugsnag, so I established bugsnag API key. here I found the solution and it still does not work.

[2022-08-12 15:24:23] laravel.EMERGENCY: Unable to create configured logger. Using emergency logger. {"exception":"[object] (InvalidArgumentException(code: 0): Log [deprecations] is not defined. at /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php:207) [stacktrace] #0 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(132): Illuminate\\Log\\LogManager->resolve() #1 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(119): Illuminate\\Log\\LogManager->get() #2 /home/shaungbhone/Desktop/find-a-pr/vendor/laravel/framework/src/Illuminate/Log/LogManager.php(108): Illuminate\\Log\\LogManager->driver()

Environment ....................................................................................................................
Application Name ....................................................................................................... Laravel
Laravel Version ......................................................................................................... 9.24.0
PHP Version .............................................................................................................. 8.1.0
Composer Version ........................................................................................................ 2.1.14
Environment .............................................................................................................. local
Debug Mode ............................................................................................................. ENABLED
URL .................................................................................................................. localhost
Maintenance Mode ........................................................................................................... OFF

Cache ..........................................................................................................................
Config .............................................................................................................. NOT CACHED
Events .............................................................................................................. NOT CACHED
Routes .............................................................................................................. NOT CACHED
Views ................................................................................................................... CACHED

Drivers ........................................................................................................................
Broadcasting ............................................................................................................... log
Cache ..................................................................................................................... file
Database ................................................................................................................. mysql
Logs ................................................................................................... stack / single, bugsnag
Mail ...................................................................................................................... smtp
Queue ..................................................................................................................... sync
Session ................................................................................................................... file

Reverts ash-jc-allen/find-a-pr#105

It seems like there are a few problems that I'm getting when deploying these changes to the server. I'm just reverting them until I can figure out what's going wrong :)