Submission Guide | Hubverse Support Toolkit

Step 1 · Before GitHub

Make sure you have the basics

You do not need to understand GitHub yet. Start with an account, your prepared submission files, and the hub you plan to submit to.

1
A GitHub accountYou should be able to sign in at GitHub.com. A GitHub username is not the same as your email address or display name.
2
Your prepared file or filesUse the Model Metadata Generator to create the metadata YAML for a new or updated model. Use the Data Preparation Tool to create and check the model-output file. This guide is the third tool: it shows you how those files move through GitHub.Tool 1 · MetadataTool 2 · Data preparationTool 3 · Submission guide
3
The hub you plan to submit toChoose the public forecasting, scenario, training, or sandbox hub named in your assignment or participation instructions on the next screen.

What is GitHub?
GitHub is the website many modeling hubs use to store files and review proposed changes. This guide will show you exactly where to click. It will not ask for your password or make changes for you.

Create a free GitHub account ↗

Step 2 · Destination

Which hub do you want to submit to?

A hub is a project that collects model outputs from many teams. Its files and instructions usually live in a GitHub project called a repository, or “repo.” Choose the exact hub named in your assignment or participation instructions.

Hub CDC influenza forecasts · weekly pull-request workflow

FluSight Forecast Hub
Selecting a hub changes the repository links, example paths, warnings, and available model-output file types throughout the guide.

See this hub on GitHub ↗Read this hub’s instructions ↗

Step 3 · Submission history

Have you submitted this model to this hub before?

Answer for this specific model and hub. Your answer changes the beginning of the walkthrough. It does not matter whether another model from your team has submitted before.

No—this is my first submission for this modelThe model does not yet have an accepted metadata entry and output folder in this hub.Detailed first-time path Yes—I have submitted this model beforeThe same model already has metadata and a model-output folder in this hub.

Choose one answer above.
Do not use your general GitHub experience to answer. A person can be new to GitHub but still work with a returning model—or know GitHub well while submitting a new model.

Step 4 · Names

Tell the guide which account and model names to show

These values only personalize paths and examples. They stay in this browser and are not sent anywhere.

Your GitHub username Enter the account name that appears in your GitHub profile address.

Where do I find my username?

Sign in to GitHub, select your profile picture in the upper-right corner, then select Your profile. If the address is github.com/alex-smith, the username is alex-smith. Do not enter your email address.

Your hub model ID This identifies the forecasting model—not you or your GitHub account.

What is a model ID, and where do I find it?

A model ID is the short name used for the model’s metadata file, output folder, and forecast filename. It often looks like team-model.

Why the earlier question matters
First-time models choose a proposed ID using the hub’s current naming rules. Returning models copy the existing ID exactly. The walkthrough will show the correct route for your answer.

Open this hub’s metadata instructions ↗Search existing model IDs ↗

Only practicing? Use clearly marked sample names now; you can replace them later.

Step 5 · Forecast file

Describe the model-output file you prepared

The guide uses these two values to demonstrate the filename and folder. Use the values required by the hub, not guesses.

Reference date Format: YYYY-MM-DD. The guide starts with the Saturday that ends the current week.

What is the reference date?

The reference_date identifies the point in time from which the model output is considered to originate. It is not automatically the upload date. For weekly Saturday-based hubs, it is usually the Saturday ending the current forecast week. Always confirm the selected hub’s allowed date in its current instructions.

File type Only formats supported by the selected hub are shown.

How can I tell which file type I have?

Look at the end of the filename on your computer. A file ending in .csv is CSV; one ending in .parquet is Parquet. This menu changes with the selected hub, but the hub’s current instructions remain authoritative.

Need to restore the suggested date after changing it?

Check the hub’s date rules ↗

Step 6 · GitHub method

How would you like to follow the GitHub steps?

If you have never used GitHub, choose the website. The other options assume software or terminal experience.

GitHub websiteUse a web browser and click buttons. Nothing to install.Choose this if new GitHub DesktopRequires the GitHub Desktop app and files saved on your computer. Command lineRequires Git, GitHub CLI, and comfort typing terminal commands.

Your walkthrough will use

FluSight · GitHub website · sample placeholders

Instructions only

Take one clear step at a time.

Set up your walkthrough

Make sure you have the basics

Which hub do you want to submit to?

Have you submitted this model to this hub before?

Tell the guide which account and model names to show

Describe the model-output file you prepared

How would you like to follow the GitHub steps?

Open the hub before you prepare the pull request.

Guide sources and scope

A practice space for the GitHub submission workflow.

What it does

What it does not do

Where it fits

Accuracy, AI-generated visuals, and scope

How-To Tutorial: the submission path

GitHub screenshot

Expanded walkthrough