Skip to main content

GHW event setup

Global Hack Week (GHW) events have special conventions in Avo, because swag eligibility is derived from how the event's challenges are configured. These are event-level features (the one-click actions live on the Event record), so set them up here.

Swag eligibility​

  • Basic swag — the hacker must complete all featured challenges. So any challenge you definitely want hackers to submit to should be marked Featured — that is what makes it required for the event. (This is why the Address challenge is always featured.)
  • Bonus swag — on top of all featured challenges, the hacker must also check in to 5 mini events. For those check-ins to count, each GHW mini event must have its parent event set to the main GHW event. If the parent isn't set, the check-in won't count toward bonus swag.

Set a mini event's parent​

The parent is set in Organizer HQ, not Avo:

  1. Open the mini event in the OHQ admin page.
  2. Select the main GHW event as the Parent.
  3. Click Update Settings.

See Organizer HQ event settings.

One-click GHW challenge actions​

Two challenges are needed for almost every GHW event, so they have dedicated one-click actions on the Event record in Avo.

note

These actions only appear once the event has a broadcast ID set (i.e. it's a GHW event). If you don't see the buttons, set the event's broadcast ID first. You'll find each as a row-control button on the Event (show/index) and in the Event's Actions dropdown.

Create Address Challenge​

One click, no inputs. It creates the "Fill out our Address Form" challenge and attaches it to the event with:

  • Type: Short Form
  • Featured: on (so it gates basic swag)
  • Active: on
  • Auto Approve: on
  • External Submission URL: https://my.mlh.io/settings
  • Is this Address Challenge?: enabled

After it runs, the success message reminds you to upload a banner image (1024 × 720) and verify the tags — the action doesn't set those.

Create GitHub Challenge​

One click with a single "Feature this challenge?" prompt. It always creates the primary challenge and attaches it to the event:

  • "Signup for the GitHub Student Developer Pack" (primary) — Type Overall, screenshots required, featured according to your prompt.

When you choose Featured = yes, it also creates the "Cannot Sign up for GitHub Student Developer Pack" backup challenge (Type Overall, not featured) and wires it as the primary's Backup Challenge, so a "cannot sign up" submission still counts toward the featured requirement. When you choose Featured = no, only the primary is created (the backup only matters for swag eligibility, which requires a featured challenge).

After it runs, upload a banner and verify the sponsorship/tags. Choose Featured = yes when you want the GitHub challenge to count toward basic swag for that event.