zulip notification

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, tooling

Research direction

Start by reviewing the README discussion about Zulip notification and toolchain release tagging, then inspect how lake new deploys project infrastructure. Define the centrally updatable actions and the configuration lines that projects should uncomment; done means both steps can be deployed through lake new without copying configuration blocks into each project.

Written by the indexing model from the issue text.

Description

priority-low

Kim says:

Kim: I agree it is best that lean-update itself doesn't do the zulip notification or toolchain release tagging. But we may want to package these steps as actions, too!
Asei: Is it not enough to add an example to the README?
Kim: Because no one should ever have to read the README, or know the repository exists. All this infrastructure needs to be deployed by lake new, and the only configuration required to uncommenting some lines. We don't want to be copy-pasting these configuration blocks into everyone's lake projects if they can be factored out into a centrally updatable action.

Dominant language
Lean
Stars
7
Forks
7
Avg merge
4h 28m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from leanprover-community/lean-update

All issues in leanprover-community/lean-update

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.