Skip to content

Commit 2b3a848

Browse files
lbarcziovamajamassarinimfocko
committed
Apply suggestions from code review
Co-authored-by: Maja Massarini <2678400+majamassarini@users.noreply.github.com> Co-authored-by: Matej Focko <mfocko@users.noreply.github.com>
1 parent 836bb59 commit 2b3a848

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

src/pages/flock-2025-workshop.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,26 +16,26 @@ By the end of this session, you should have a working configuration that automat
1616

1717
### Prerequisites
1818

19-
- Ensure you have a **Fedora package** you maintain/co-maintain. Ideally, pick one that has a **pending upstream release**, as this allows trying things out easily.
19+
Ensure you have a **Fedora package** you maintain/co-maintain. Ideally, pick one that has a **pending upstream release**, as this allows trying things out easily.
2020

2121
### Setup
2222

23-
For detailed setup instructions, you can follow [the documentation](https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding#setup). You can find a brief summary below:
23+
For detailed setup instructions, you can follow [the documentation](https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding#setup). You can find a brief summary below.
2424

2525
#### Create a working branch
2626

2727
Before creating the configuration file, review [this section on how you'll be trying out the setup](https://packit.dev/docs/fedora-releases-guide/dist-git-onboarding#release-syncing).
28-
Based on that, create a new branch in your dist-git repository for your Packit configuration
28+
Based on that, create a new branch in your dist-git repository (it's also recommended to do this in fork) for your Packit configuration
2929
(e.g., `packit-setup`).
3030

3131
#### Create the Packit configuration file
3232

3333
Packit uses a YAML configuration file, named `(.)packit.yaml`, to define its behavior. This file needs to be placed in your **dist-git repository**,
34-
in general in the `rawhide` branch, but for experimentation during the workshop in a new branch, trying things out in a pull request.
34+
in general in the `rawhide` branch, but for experimentation during the workshop in a new branch, to be able to try running the jobs from an open pull request.
3535

3636
Then, the simplest ways of creating the config:
3737

38-
- Use `packit dist-git init` (requires `packit` installed locally, e.g. `dnf install packit`)
38+
- Use `packit dist-git init` (requires `packit` installed locally, e.g., `dnf install packit`)
3939

4040
1. In your cloned dist-git repository, switch to the target branch.
4141
2. Run the command:

0 commit comments

Comments
 (0)