make-release
Skill1.3k starsChanged 20 days agoLicence not identifiedView on GitHub
Make an LFortran release end-to-end: require the tip of main to have its own green Quick and Exhaustive push runs (send fix PRs if not, but never release red main), create the vX.Y.Z tag and GitHub release with generated notes, verify the CI-uploaded tarball, update conda-forge/lfortran-feedstock from the user's fork (rerender, automerge, packaging patches until green, then upstream every patch to LFortran main), and update lfortran/lfortran-conda-testing until green (workarounds or disabled steps linked to filed issues, with fix-issue PRs to main for every regression). Use when asked to make, cut, publish, or finish a release or a new version. Ends by printing the version announcement with the release and both PR links. Not for release-policy discussions or CI changes unrelated to a release.
- Commits and pushes
6 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- ocicl/ocicltheir own version, first seen Oct 9, 2026
- atgreen/cl-tuitiontheir own version, first seen Oct 8, 2026
- tradingstrategy-ai/web3-ethereum-defitheir own version, first seen Oct 8, 2026
- atgreen/icltheir own version, first seen Oct 8, 2026
- quarto-dev/quarto-clitheir own version, first seen Oct 8, 2026
- hathach/tinyusbtheir own version, first seen Oct 8, 2026
Who's talking about lfortran/lfortran
- @ondrejcertik.bsky.social“LFortran has just reached 1,000 stars on GitHub. github.com/lfortran/lfo...”Bluesky · Jan 7, 2025 · 21 likes
- lcompilers/lpython“GSoC Ideas”GitHub · Jan 31, 2024 · 5 reactions
- lcompilers/lc“Some benchmarks”GitHub · Dec 21, 2023 · 3 reactions
- rouson/assert“Get tests working”GitHub · Jun 19, 2025 · 2 reactions
- scipy/scipy“BUG? Incorrect branch in `LAMV` / `_specfunc.lamv`”GitHub · Sep 28, 2022 · 2 reactions
The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 51
Talked about on GitHub and Bluesky (51 times).
On GitHub · 50
- Jan 31, 2024GSoC Ideas — lcompilers/lpython5 reactions
- Dec 21, 2023Some benchmarks — lcompilers/lcsays it tested it3 reactions
- Jun 19, 2025Get tests working — rouson/assert2 reactions
- Sep 28, 2022BUG? Incorrect branch in `LAMV` / `_specfunc.lamv` — scipy/scipy2 reactions
- Aug 4, 2026Expand and enhance native-multi-image test — BerkeleyLab/caffeine1 reaction · 2 comments
45 more on GitHub
- Jun 24, 2026LFortran 0.58.0 fails to compile project — toml-f/toml-f1 reaction
- Jun 3, 2026[NO REVIEW] CI: Enable native testing for lfortran:latest — BerkeleyLab/caffeinesays it tested it1 reaction
- Jan 28, 2026[Feature] : Add utility/magic command to print out the PTU/LLVM IR/WASM Module generated per cell — compiler-research/xeus-cpp1 reaction · 2 comments
- Mar 18, 2025Remove C-Wrapper for MPI_Init — lfortran/fortran_mpi1 reaction · 3 comments
- Sep 3, 2024Compile with LFortran — modern-fortran/neural-fortran1 reaction
- Oct 28, 2023[SciPy]: Test compiled packages at CI — lfortran/lfortran-conda-testing1 reaction · 2 comments
- Jul 3, 2023Implement physical types for arrays — lcompilers/lpython1 reaction · 2 comments
- Feb 10, 2023Compile and run ``picoGPT/gpt2.py`` — lcompilers/lpython1 reaction · 4 comments
- Nov 19, 2022Sync libasr with LCompilers — lcompilers/libasr1 reaction · 1 comment
- Sep 28, 2022FIX: special: use intended branching for `lamv` implementation — scipy/scipy1 reaction · 5 comments
- Aug 9, 2022Improving ASR passes infrastructure — lcompilers/lpython1 reaction · 2 comments
- Nov 6, 2026Fix out-of-bounds read of s_dims in rdh5 — predsci/POT3D0 reactions · 3 comments
- Oct 27, 2026lfortran: add newer versions — spack/spack-packages0 reactions
- Oct 26, 2026feat: serve a session with a built-in Jupyter kernel — certik/lfortran0 reactions · 1 comment
- Oct 13, 2026fix: preserve DTIO child output positions — certik/lfortran0 reactions · 1 comment
- Oct 9, 2026an earlier parameter statement makes a later variable constant — ubaidsk/lfortran0 reactions
- Oct 9, 2026a hollerith apostrophe in a format fails the tokenizer — ubaidsk/lfortran0 reactions
- Oct 9, 2026a fixed form namelist statement is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a pause statement makes the next line unexpected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a file of only an asterisk comment fails in the tokenizer — ubaidsk/lfortran0 reactions
- Oct 9, 2026a real literal with exponent letter q is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a parameter list without parentheses is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a character length after an array name is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a two argument function named diff is treated as the intrinsic — ubaidsk/lfortran0 reactions
- Oct 9, 2026a hollerith constant is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026an exit from a named select case is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026an iomsg that is a character component is rejected — ubaidsk/lfortran0 reactions
- Oct 9, 2026a select type guard rejects its construct name — ubaidsk/lfortran0 reactions
- Oct 5, 2026Complex kind 16 is rejected — ubaidsk/lfortran0 reactions
- Oct 5, 2026A preprocessor bang after an ampersand fails — ubaidsk/lfortran0 reactions
- Oct 4, 2026An interface block needs a program statement — ubaidsk/lfortran0 reactions
- Sep 13, 2026Check test images against stored fuzzy fingerprints — fortran-lang/fplotlib0 reactions · 4 comments
- Sep 8, 2026[NO REVIEW] CI: Update native-multi-image to cover derived-type pod — BerkeleyLab/caffeine0 reactions
- Sep 3, 2026Add collectives test coverage for non-contiguous arrays — BerkeleyLab/caffeine0 reactions
- Aug 28, 2026Relax clang and zstd run deps — conda-forge/lfortran-feedstock0 reactions · 3 comments
- Aug 22, 2026[NO REVIEW] CI: Minor tweaks — BerkeleyLab/caffeine0 reactions
- Aug 18, 2026Fix: work around lfortran issue 12521 — BerkeleyLab/julienne0 reactions
- Aug 12, 2026Send the service worker heartbeat under the base URL — jupyterlite/jupyterlite0 reactions · 2 comments
- Jul 30, 2026[NO REVIEW]: CI: Enable HAVE_COBOUND for lfortran-latest — BerkeleyLab/caffeine0 reactions
- Jul 26, 2026[NO REVIEW] CI: Add sync team in lfortran-latest — BerkeleyLab/caffeine0 reactions
- Jul 23, 2026[NO REVIEW] CI: Enable FORM TEAM testing for lfortran-latest — BerkeleyLab/caffeinesays it tested it0 reactions
- Jul 18, 2026LFortran — jacobwilliams/json-fortran0 reactions · 2 comments
- Jul 13, 2026[NO REVIEW] app/native-multi-image: Enable LFortran testing of module coarray initialization — BerkeleyLab/caffeinesays it tested it0 reactions
- Jul 10, 2026[NO REVIEW] CI: Enable `SYNC IMAGES` for lfortran-latest in native-multi-image — BerkeleyLab/caffeine0 reactions
- Jul 9, 2026native-multi-image: Add coverage for coarray initialization — BerkeleyLab/caffeine0 reactions
On Bluesky · 1
- Jan 7, 2025LFortran has just reached 1,000 stars on GitHub. github.com/lfortran/lfo... — @ondrejcertik.bsky.social21 likes and reposts
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- hathach/tinyusb★ 7.3ksame name
- quarto-dev/quarto-cli★ 6.2ksame name
- tradingstrategy-ai/web3-ethereum-defi★ 830same name
- ocicl/ocicl★ 318same name
- atgreen/icl★ 200same name
- atgreen/cl-tuition★ 149same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- classify-issueSkill
- create-mreSkill
- fix-issueSkill
- fix-mreSkill
- pr-reviewSkill
- repro-issueSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 8 are distinctive, and 18 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
18
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.