Test for clreq notifications: Please ignore
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 809
- Forks
- 66
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
This is to test whether the notification mechanism is working for issues in this repository. A test will be set up for each repository in order to iron out some irregularities in recent notification digests.
Settings/Webhooks has https://labs.w3.org/snapshot-generator/payload
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is explicitly a notification-mechanism test and asks readers to ignore it. It mentions Settings/Webhooks and the snapshot-generator payload, but defines no project change or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 1/100