set -euo pipefail

if [[ -z "${NEWSLETTER_MONTH}" ]]; then

echo "NEWSLETTER_MONTH is not set. Exiting..."

exit 1

if [[ -z "${NEWSLETTER_YEAR}" ]]; then

echo "NEWSLETTER_YEAR is not set. Exiting..."

exit 1

if [[ -z "${NEWSLETTER_DEADLINE}" ]]; then

echo "NEWSLETTER_DEADLINE is not set. Exiting..."

exit 1

if [[ -z "${NEWSLETTER_COUNTER}" ]]; then

echo "NEWSLETTER_COUNTER is not set. Exiting..."

exit 1

cp newsletter-template.md index.md

sed -i "s/{{\s*NEWSLETTER_MONTH\s*}}/${NEWSLETTER_MONTH}/g" index.md

sed -i "s/{{\s*NEWSLETTER_YEAR\s*}}/${NEWSLETTER_YEAR}/g" index.md

sed -i "s/{{\s*NEWSLETTER_DEADLINE\s*}}/${NEWSLETTER_DEADLINE}/g" index.md

sed -i "s/{{\s*NEWSLETTER_COUNTER\s*}}/${NEWSLETTER_COUNTER}/g" index.md

destination="content/news/$(printf "%03d" ${NEWSLETTER_COUNTER})"

mkdir -p $destination

mv index.md $destination/index.md

git status

title: "Newsletter {{ env.NEWSLETTER_COUNTER}}: {{ env.NEWSLETTER_MONTH }} {{ env.NEWSLETTER_YEAR }}"

labels: coordination, help wanted

assignees: janhohenheim

**Editors:**

Another month has gone by, so it's time to put together the Rust Gamedev

newsletter with {{ env.NEWSLETTER_MONTH }}'s news!

The deadline for all section PRs is the **03.{{ env.NEWSLETTER_DEADLINE }}**

We _may_ still accept PRs that are submitted later than this, as long as they're

ready before the newsletter's release, but this isn't guaranteed.

If you want your section to be included, don't leave it till the last minute!

Below is our current planned structure for the newsletter,

and the status of each PR (which we'll try to keep updated).

This is **not** an exhaustive list - if you have your own project that you want

to write about, just make a comment on this issue and open a PR!

- TODO

- TODO

- TODO

- TODO

- TODO

- TODO

- TODO

- [ ] Final review - by everyone

- [ ] Publish - by @janhohenheim

- [ ] Post on /r/rust, /r/rust_gamedev, /r/gamedev, URLO - by @janhohenheim

- [ ] Pin thread on Twitter - by @AngelOnFira

- [ ] Add comment links - by @AngelOnFira

If you want to help writing the newsletter:

- **Read [CONTRIBUTING.md](https://github.com/rust-gamedev/rust-gamedev.github.io/blob/source/CONTRIBUTING.md?rgh-link-date=2023-09-12T16%3A17%3A34Z).**

- Choose one or more of the "🆓 **free**" sections listed below, and leave a

comment letting us know you want to work on them.

- The links in brackets (like `[1](#), [2](#), [3](#)`) are suggestions of

links to include in the section. Feel free to add more!

- The username listed next to the section (like `@janhohenheim?`) is a

suggestion of who may want to pick up the work (usually the project's

developer, or someone who has expressed interest in the past).

- You are not obligated to write a section if you're tagged or your project

is listed! You're welcome to ask someone else to write the section,

or to ask for your project to be excluded from this month's post.

- Extra sections not listed in the plan are welcomed -

just leave a comment and open a PR!

- Write a short overview in the newsletter's Markdown file,

making sure to follow the style guidelines (see below).

- Send a PR _to the `source` branch_ (example: [N15: A/B Street #336](https://github.com/rust-gamedev/rust-gamedev.github.io/pull/336)).

- Mention this issue in your PR's description to link it all together.

The full style guide is in [CONTRIBUTING.md](https://github.com/rust-gamedev/rust-gamedev.github.io/blob/source/CONTRIBUTING.md?rgh-link-date=2023-09-12T16%3A17%3A34Z),

but here are the most important rules:

- Write in third-person perspective.

- Each line must be 80 characters or less, for ease of reviewing/diffing.

- Only one image per section is allowed.

- The maximum size is 300kb for static images and 2.5mb for GIFs.

- The image should come before the text, and must have alt text for accessibility.

- Prefer static images to GIFs, to keep the page load times down.

- Each section should be under 1000 characters, and under 6 paragraphs.

- This only applies to the rendered text, not the markup.

- Keep formatting minimal - no bold/italics/etc.

- Avoid long/nested bullet point lists - no changelogs!

Please use these templates as a starting point:

**Games/apps/libraries:**

### [Game name]


_optional image label_

[Game name] ([GitHub], [Discord], [Twitter]) by [@nickname]

is... {short project description in one sentence}.

{An overview of the recent updates with links to more details}.

_Discussions: [/r/rust_gamedev](link), [Twitter](link), [etc](link)_

[Game name]: http://example.com

**Articles/blog posts/videos/etc:**

### [Article name]


_optional image label_

[@nickname] published an [article] about...

{overview what the resource is about}.

_Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_

[Article name]: http://example.com

name: Create Newsletter

on:

schedule:

# Run on the 5th of every month at 12pm

- cron: "0 12 5 * *"

workflow_dispatch:

inputs: {}

permissions:

contents: write

issues: write

jobs:

create-newsletter:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v3

with:

ref: source

- name: Set environment variables

run: |

- name: Create newsletter scaffold

run: ./.github/create_newsletter_scaffold.sh

- name: Commit and push changes

uses: EndBug/add-and-commit@v9

with:

message: "Create newsletter N${{ env.NEWSLETTER_COUNTER }} for ${{ env.NEWSLETTER_MONTH }} ${{ env.NEWSLETTER_YEAR }}"

push: "origin HEAD:source"

- name: Create tracking issue

uses: JasonEtco/create-an-issue@v2

env:

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

with:

filename: .github/newsletter-issue-template.md

title = "This Month in Rust GameDev #{{ NEWSLETTER_COUNTER }} - {{ NEWSLETTER_MONTH }} {{ NEWSLETTER_YEAR }}"

date = {{ NEWSLETTER_DEADLINE }}

Welcome to the {{ NEWSLETTER_COUNTER }}th issue of the Rust GameDev Workgroup's