4. Submitting Your Art

A no-command-line GitHub workflow.

Fork, Branch, Upload, Pull Request

Submitting your art through GitHub

1. Make an account: https://github.com/signup

2. Open https://github.com/gitupofftheflooranddosomework/millsberry.com and click Fork → Create fork.

3. Create a branch such as art/millsberry-logo, art/base-citizen, art/stat-icons, or art/mayor-trumble.

4. On that branch use Add file → Upload files. Include finished PNG, native layered source, SVG if applicable, and useful reference screenshots.

5. Do not upload over official-recovered-assets.

6. Click Contribute or Compare & pull request and propose your branch into the main repo.

In the PR say what you made, what original references/SWFs/pages you used, anything you had to guess, and your Discord name if different.

Contribution notes: https://github.com/gitupofftheflooranddosomework/millsberry.com/blob/main/CONTRIBUTING.md

What Happens After You Open a Pull Request?

What happens after you open a pull request?

Opening a pull request does not immediately change the live game.

It is basically you saying:

Here is what I made and I would like to add it to Millsberry Reborn.

The team can review the files, compare them against the references, and suggest changes if anything needs adjusting.

You do not need a new PR for every revision

If you update files on the same branch in your fork, the pull request updates automatically.

That means the normal flow is:

  1. Open one branch for the art item.
  2. Open one pull request.
  3. Make any requested changes on that same branch.
  4. The existing pull request updates.
  5. Once everybody is happy, a maintainer merges it.

Include useful context

In the pull request description, tell us:

This history is useful later when somebody asks where a recreated asset came from or why a design choice was made.