Skip to content

Git Action that creates the event.md files #27

Open

Description

@snohio

Git Action that creates the event.md files

User Story

As a member of Orlando Devs group, I would like a GitHub Action that requires input from the Organizer that creates the meetup.md file so that Organizers do not have to create the markdown event file manually and submit the PR.

Tasks

Many many tasks. Fill these out as we go!

  • Create a GitHub Action that accepts the following inputs:
    • GROUP_NAME (should be a picklist of pre-registered groups found in /src/data/groups.json)
    • DATE (in YYYY-MM-DD format with validation if possible)
    • START_TIME ("10AM")
    • END_TIME
    • SUBJECT
    • ADDRESS
    • GOOGLE_MAPS_URL
    • PRICE (optional)
    • EVENTBRITE_MEETUP_LINK
    • SHORT_DESCRIPTION
    • PARKING_DETAILS
    • TALK_TITLES (array of strings)
    • AUTHOR_INTRODUCTION (array of strings)
  • Check out a new branch using the name of the event
  • Using the provided inputs, generates an output file using the input values on the template
  • Names that file YYYYMMDD-subject-of-event.md and saves it to /src/content/events/
  • Opens a pull request that targets the incoming-events branch (see discussion)

Extra Notes

Loads to discuss here. Some additional parameters to consider.

  • Do we need a function to upload an image or can we (should we) just point to an existing URL.
  • Once submitted, this should create a branch and then a PR. I don't believe the PR can happen to Main right now, but we can talk about that. COmmitting directly to main could allow for outside individuals posting events without approval.
  • Let's see if we can limit posting to the @OrlandoDevs/board-of-advisors . If we can, direct publishing without approval might be better.

You can reference https://github.com/OrlandoDevs/website/blob/main/src/content/events/ci-cd-pipeline-deep-dive.md?plain=1 as an example of the inputs needed. These will go into /src/content/events/ path.

Activity

  1. wgeorgecook commented on Jan 24, 2025

    @wgeorgecook
    Collaborator

    @snohio I think I enumerated exactly what we need for the action to be successful in the checklist. Can you read it through and see if I missed anything?

  2. wgeorgecook commented on Jan 24, 2025

    @wgeorgecook
    Collaborator

    Personally I think we should map group name to image url and host them internally here to prevent any old image from getting linked. The TTP for that I'm sure is not very long.

  3. wgeorgecook commented on Jan 25, 2025

    @wgeorgecook
    Collaborator

    I'm working on this now.

  4. wgeorgecook commented on Jan 25, 2025

    @wgeorgecook
    Collaborator

    Invalid workflow file: .github/workflows/new_event.yaml#L1
    you may only define up to 10 inputs for a workflow_dispatch

    Well this is not documented in anything I was reading. We'll have to simplify or find a workaround.

  5. snohio commented on Jan 28, 2025

    @snohio
    CollaboratorAuthor

    How many inputs are we asking for?
    Oh. It looks like 12.. Sigh.. Um...

  6. snohio commented on Jan 28, 2025

    @snohio
    CollaboratorAuthor

    We don't have to be prescriptive of the details. It does need to be able to accept and save markdown. Can we systematically pull an link from Google maps based on the address? We might be able to forgo price and make it FREE. If someone needs to charge for an event, we can modify the actual event markdown and republish. That will impact the next step of creating the EventBrite event through APi..

  7. snohio commented on Jul 2, 2025

    @snohio
    CollaboratorAuthor

    Can we utilize AI for this?I have been using CoPilot to create the events based on other events from the information on Meetup or Lu.ma and it has worked rather well. The only issue is that the description needs to be short, and it is the full description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions