@driesvints, you may need to test this locally as I can't see the ad sense ads. They seem to be taking up around about the right amount of space, but would be nice to see them rendered. I think it's just the homepage, sidebar and footer I can't see.

I'm working on the notifications, we need that to #271, #270 and #279. But I'm not a good designer, so I need help before getting deep into it xd

It's using vue, he will turn the job easier later.

This is how it looks now

The first one are in the hover state, the last one are marked as read.

This pull request includes the changes for upgrading to Laravel 8.x. Feel free to commit any additional changes to the shift-35839 branch.

Before merging, you need to:

• Checkout the shift-35839 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 8
• Run composer update (if the scripts fail, add --no-scripts)
• Thoroughly test your application (no tests?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

This pull request includes the changes for upgrading to Laravel 5.8. Feel free to commit any additional changes to the shift-19040 branch.

Before merging, you need to:

• Checkout the shift-19040 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 5.8
• Run composer update (if the scripts fail, add --no-scripts)
• Thoroughly test your application (no tests?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

This pull request includes the changes for upgrading to Laravel 5.5. Feel free to commit any additional changes to the shift-4820 branch.

Before merging, you should:

• Checkout the shift-4820 branch
• Review all pull request comments for additional changes
• Run composer update (if the pre-commands fail, add --no-scripts)
• Thoroughly test your application

If you would like more help with your upgrade, check out the human services from Laravel Shift. If you need to level-up your Git skills, check out Getting Git.

See image: http://i.imgur.com/eRkcCLe.png - Notice the scroll bar at the bottom. I get this problem in Chrome (Windows and Linux), FireFox (only tested Windows) and Internet Explorer 11.

This seems to be related to the css of body.bin .show-container { width: 200%; overflow-x: scroll; }

If I remove either the 200% width or the overflow-x things immediately look better. To get rid of the scrollbar at the bottom I need to do overflow-x: hidden on body, which I'm sure is not the intent.

These changes were introduced in #105 and I'd love to hear more reasoning behind them. Were they even tested?

This pull request includes the changes for upgrading to Laravel 7.x. Feel free to commit any additional changes to the shift-24472 branch.

Before merging, you need to:

• Checkout the shift-24472 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 7
• Run composer update (if the scripts fail, add --no-scripts)
• Thoroughly test your application (no tests?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

This pull request includes the changes for upgrading to Laravel 5.6. Feel free to commit any additional changes to the shift-6274 branch.

Before merging, you should:

• Checkout the shift-6274 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 5.6
• Run composer update (if the pre-scripts fail, add --no-scripts)
• Thoroughly test your application

If you need help with your upgrade, check out the Shift Human Services or join the Shifty Coders Slack room to get answers to all your Laravel questions.

This pull request includes the changes for upgrading to Laravel 9.x. Feel free to commit any additional changes to the shift-60141 branch.

Before merging, you need to:

• Checkout the shift-60141 branch
• Review all pull request comments for additional changes
• Run composer update (if the scripts fail, add --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

Hey there!

I belong to an open source security research community, and a member (@hdvinnie) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

This pull request contains changes for migrating your test suite from PHPUnit to Pest automated by the Pest Converter.

Before merging, you need to:

• Checkout the shift-49229 branch
• Review all of the comments below for additional changes
• Run composer update to install Pest with your dependencies
• Run vendor/bin/pest to verify the conversion

We should add some documentation for the new API sent in at https://github.com/laravelio/laravel.io/pull/793.

I'm not sure if we should use a certain API documentation tool or just try to incorporate it into the current design.

Users should be able to connect or disconnect their GitHub account after creating their account. Should be a new box on the settings page. Connecting their GitHub account will fill in their GitHub username.

Explain why we ask to connect their GitHub account (as opposed to let them fill in a text field for their username):

1. We offer social authentication this way
2. We use their GitHub account to verify they're real persons (and not bots)
3. We integrate with GitHub for upcoming features

Filter out any duplicates with:

SELECT
    github_username,
    COUNT(github_username)
FROM
    users
GROUP BY
    github_username
HAVING
    COUNT(github_username) > 1;

SELECT
    *
FROM
    users
WHERE
    github_username = 'duplicate';

These can actually be synced from their GitHub ID. We should run a queued job that goes over all accounts and syncs them. Maybe also a scheduled job or a GitHub webhook.