Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

💸 Payout #8

Open
Tracked by #1
zspencer opened this issue Jan 15, 2024 · 0 comments
Open
Tracked by #1

💸 Payout #8

zspencer opened this issue Jan 15, 2024 · 0 comments

Comments

@zspencer
Copy link
Member

No description provided.

This was referenced Jan 15, 2024
Open
Open
@zspencer zspencer mentioned this issue Jan 29, 2024
Open
zspencer added a commit that referenced this issue Feb 12, 2024
@zspencer
✨ Journal: Author provides Entry#summary (zinc-collective#2161)
64cc4aa 
- When zinc-collective#2, add an zinc-collective#10 so we can eventually display it when zinc-collective#4


* 🧹🥗 `Journal`: Add `Entry#summary` field (#8)

- zinc-collective#10

What I'm driving towards here is similar to
zinc-collective#2055, where a
`Journal::Entry` has an affordance for being opinionated about how it's
represented when linked to in search engines or peer-to-peer sharing; as
well as short text for when there are a several on `Journal#show`.

* 🛠️ `Journal`: Test only the `Journal in CI

While working on
zinc-collective#11, I realized I
missed a piece of the refactor because I was leaning-on-ci as a way to
confirm that everything was working as expected.

Little did I know, CI was not working in this fork. Which makes sense,
because you don't want to automatically turn on all the Workflows when
you fork a project.

This adds a Github Workflow for testing *just* the `Journal`, which
should make detecting oopsie-daisys a bit easier for folks who are only
interested in working on the Journal.

* 🥗 `Journal`: Test adding `Entry#summary` when Writing `Entries`

- zinc-collective#10
- zinc-collective#2

This is a quick line-of-action end-to-end test for setting an `Entry#summary`.

* ✨ `Journal`: Save `Entry#summary` when Writing `Entries`

- zinc-collective#2
- zinc-collective#10

And just like that, there's a `Summary` field on the
`Journal::Entry#new` page!
zspencer added a commit that referenced this issue Feb 12, 2024
@zspencer
🥗 Tobais: Spec for Issuing a Payout
687167d 
- #11
- I'm "presuming" that a single #9
  may wind up managing multiplehttps://github.com//issues/4
- This sketches out the pathway for creating a #8
  via the Web
@zspencer zspencer mentioned this issue Feb 12, 2024
Merged
zspencer added a commit that referenced this issue Feb 27, 2024
@zspencer
🥗 Tobais: Spec for Issuing a Payout
91df859 
- #11
- I'm "presuming" that a single #9
  may wind up managing multiplehttps://github.com//issues/4
- This sketches out the pathway for creating a #8
  via the Web
zspencer added a commit that referenced this issue Mar 25, 2024
@zspencer
🥗 Tobais: Spec for Issuing a Payout
b1b3055 
- #11
- I'm "presuming" that a single #9
  may wind up managing multiplehttps://github.com//issues/4
- This sketches out the pathway for creating a #8
  via the Web
@zspencer zspencer mentioned this issue Mar 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zspencer