Skip to content

Conversation

incertum
Copy link
Contributor

update: README.md and CONTRIBUTING.md

Fixes #148

CC @ktoso @heckj

@incertum incertum added the semver/none No version bump required. label Sep 29, 2025

When you create a bug report, please provide the following:

- **swift-prometheus commit hash** you are using.
Copy link

Choose a reason for hiding this comment

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

All great detail, and we should include a PR template that specifically asks for this detail as well

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was thinking about it. Let’s keep track of creating a more formal template in /swiftlang or /apple?

(We are currently exploring the possibility of having this client accepted into the Prometheus project. Consequently, the Contributing guidance may undergo further modifications if this outcome materializes.)

```

- **Simulate CI Workflows (Optional)**: For a more comprehensive check, you can run the full GitHub Actions workflows locally using [act](https://github.com/nektos/act). This is useful for catching issues that only appear in the CI environment.
- For detailed setup instructions, see the Swift project's guide on [Running Workflows Locally](https://github.com/swiftlang/github-workflows?tab=readme-ov-file#running-workflows-locally).
Copy link

Choose a reason for hiding this comment

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

I tried the whole sequence with act and really struggled to get it working with anything OTHER than docker-desktop - I love the concept of describing this and providing a means to check the workflows locally, but it was particularly cranky for me.

I'm not immediately clear on what other options there might be, or how to make that process work a bit more smoothly - say for example, using container instead of docker and what might need to exist to arrange that. That's probably beyond the scope of this edit though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's probably beyond the scope of this edit though.

I would say so, yes.

Should we open a new issue against https://github.com/swiftlang/github-workflows?tab=readme-ov-file#running-workflows-locally just to keep track of the callouts?
(We should consider proposing various cross-platform solutions.)

@ktoso
Copy link
Collaborator

ktoso commented Oct 7, 2025

I unbroke the nightly benchmarks; #153

@heckj
Copy link

heckj commented Oct 9, 2025

Lgtm

@incertum
Copy link
Contributor Author

Lgtm

Thanks @heckj!
@ktoso may I kindly ask for your review? Thanks in advance!

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

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Contributing guidance and polish README

3 participants