dev-posts-to-jekyll-markdown-action

• Cleans up the cover image formation for the markdown to return a useable URL for your Jekyll site
• Update README instructions to point to main branch

This version fixes the deprecated function calls from the Octokit Rest API. The previous versions no longer work.

• Various bug fixes

Changes:

• This is a breaking change: It no longer functions by removing old posts from your Jekyll blog to keep to a limited number of blog posts there
• Adds the blog post markdown from DEV to the new file on the Jekyll blog

Fixes an issue with loading the secrets from the secrets list in the repository and also fixes a typo

Remove extraneous indentation from the creation of the new markdown file.

Note: This is a breaking change.

The action now requires the usage of your repository secrets to define certain additional values. Namely, you now must define REPO and REPO_OWNER in your GitHub repository. This is done to make the experience consistent whether you use the action on a cron schedule or triggered by an event, since the payloads from GitHub are different across those types.

This release is a breaking change. It refactors how the information for repository owner, name and master branch SHA is gathered. This was done so that the information can be gathered regardless of whether the context of the action is a pull request or a cron job.

v0.01 of Action Released 🎉