Stay signed in longer?

To address the issue of being logged out too quickly when signed in via GitHub, you can consider the following solutions:

1. Session Timeout Configuration: If you have control over the application, you can adjust the session timeout settings. This is typically done in the server-side configuration. For example, in a Laravel application, you can set the session lifetime in the config/session.php file:

   'lifetime' => 120, // Set the session lifetime to 120 minutes
   

   This will keep the user logged in for 2 hours. You can increase this value to suit your needs.

2. Remember Me Functionality: Implement a "Remember Me" feature that allows users to stay logged in for a longer period. This usually involves setting a persistent cookie. In Laravel, you can use the remember method when authenticating:

   if (Auth::attempt(['email' => $email, 'password' => $password], $remember = true)) {
       // The user is being remembered...
   }
   

   This will keep the user logged in even after the session expires, as long as the cookie is valid.

3. OAuth Token Expiry: If the issue is related to OAuth token expiry (since you're using GitHub for authentication), check the token's expiration settings. Some OAuth providers allow you to request longer-lived tokens or refresh tokens that can be used to obtain new access tokens without re-authentication.

4. Check for Application-Specific Settings: If you're using a third-party application or service, check if there are settings specific to session duration or authentication persistence. Some platforms have configurable options for session management.

If you don't have control over the application settings (e.g., if it's a third-party service like Laracasts), you might need to reach out to their support team to see if they can adjust the session duration for you.