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

Before merging, you should:

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

If you want 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.

Allows an author to add a gistlog.yml to their gist and have the following values pulled into a config file for the gist:

1. published
2. published_at
3. preview

The main goal of this PR is to allow authors to customize the preview text that is used for their gists on the author page. The other two config items will be used in future development to allow more fine grained control over the presentation and publishing of their posts.

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

Before merging, you need to:

• Checkout the shift-44295 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?)

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-16545 branch.

Before merging, you should:

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

If you want 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 5.2. Feel free to commit any additional changes to the shift-16540 branch.

Before merging, you should:

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

If you want 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.

Hello - I've created a GitHubMarkdownTransformer that uses the github-api-client to transform markdown with githubs markdown endpoint.

I updated the ContentParser class to register the new github transformer, and remove the old one.

I created a GitHubClientServiceProvider that builds the cached client and sets auth. (same as the gistClient that already existed). Registered in config/app.php. Different from gistClient is that since the authenticate() method is only setting a token, i modified the check to only look for token, instead of client_id and client_secret.

Last, i created a test that makes a call to the rate_limit api endpoint to verify auth is working by returning 5000 as the core rate limit. I modified the github-api-client to include this endpoint and have a PR open on that repo to include this addition.

Thanks.

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

Before merging, you should:

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

If you want 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.

Locked to most recent commit right now because composer wants to pull in a broken commit by default, even at dev-master. Kind of weird.

Once there's a tag or composer is actually pulling in the most recent commit, we can drop that.

Test with this gist adamwathan/b6450affd3e2cacde13d :)

fixes Issue #7 requires PR #77

This adds user creation and login through socialite with the purpose of allowing users to comment on a Gistlog post without having to leave the post itself.

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

Before merging, you need to:

• Checkout the shift-43078 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?)

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 contains changes for upgrading to Tailwind 2.x automated by Shift.

Before merging, you need to:

• Checkout the shift-46799 branch
• Review all pull request comments for additional changes
• Run npm install (if nothing installs, try removing package-lock.json first)
• Build your CSS assets
• Thoroughly review your application for additional styling tweaks

Firstly I'd like to say that I just discovered this application and it's already become my favourite way to write and publish content. Thank you so much for the work you've put in to making it. It's genuinely a delight. I'm super pumped that the repo allows contributions.

To be honest, I am a novice php/javascript developer but I wanted to contribute back to the project. So I considered the fact that it would be nice if the user's github profile blurb was displayed below their header as a way to flesh out the user's profile page a little more. I'm not sure however if the maintainers think something like that is valuable.

If the above idea isn't feasible, please let me know if there are contributions that could be made in the realms of documentation, testing, or tooling.

Thank you again for the effort.

It seems that anchors don't work once the md is viewed in gistlog. For example I just made my first blog post: https://gistlog.co/engineersamuel/858571689dc9af802a26b63b1e8a1b56 . The TLDR What worked anchor doesn't work. However if you open the gist @ https://gist.github.com/engineersamuel/858571689dc9af802a26b63b1e8a1b56 and click the What worked then the anchor works fine.

After creating a new GistLog and/or changing an existing GistLog's published status (via the gistlog.yml file), it seems to take a while for the change to take effect on my landing page. Is there an expected delay between publishing new logs and when they should appear on the landing page? Ideally, a user could change the published state and have it take effect immediately, in case they accidentally published something they wasn't ready/etc.

If I open the Gist page directly (e.g. https://gistlog.co/{user}/{id}), the content is always fresh. So it simply seems to be an issue with the landing page (e.g. https://gistlog.co/{user}). I noticed some caching being done in the landing page client, but I couldn't tell how long the cache duration was. Thanks again for making an awesome product!

In regards to our discussion on #117 or more specifically this comment, what type of settings would we want to make available to authors? Here are a few thoughts.

• Twitter Username
• Author Webpage
• Google Analytics Tracking Id (UA thingy)

Seems pretty minimal I know. Would love to hear feedback.

No idea on what the implementation would be, how things would be scored, or anything, but it would be cool if the home page could show trending posts so you can see what people are reading.

Could be an upvote system, view count, shares, who knows, but the general job story is something like:

When I'm looking for interesting tech writing to read, I want a way to discover posts that are getting a lot of attention, to help me keep up with what others are talking about in the tech community