Skip to content

Conversation

@salvadorio
Copy link

It's very casually written - not sure if that's okay. But I generally just outline some information that we should fill out over the season as we discover things, so as to avoid rediscovering them next year - no real data yet.

I'll try to figure out how to un-capitalize my branch name.

@salvadorio salvadorio requested a review from a team as a code owner January 30, 2023 18:00
Copy link
Contributor

@mattsmithtaiko mattsmithtaiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's ok for now given that you plan to add more info.

Two things:

  1. For the todo sections, can you add something like TODO(salvadorio): the thing I need to do? Then we can scrape the wiki later for all TODO statements.

  2. Can you try making the table for the rivets section? As far as making a table goes, it is a lot like ascii art, although you don't need to make it look pretty in the code. Something like

    A | B | C
    --- | --- | ---   # At least 3 hyphens per column needed here.
    Item 1 | Some info | More info
    Item 2 | I have a lot to say about item 2. | Another long block of text.
    

    produces

    A B C
    Item 1 Some info More info
    Item 2 I have a lot to say about item 2. Another long block of text.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants