1lab/mikan
13
52
Fork
You've already forked mikan
9

chore: update HACKING.md #47

Merged
amyliao merged 2 commits from pounce/mikan:update-hacking into main 2026年04月28日 19:53:54 +02:00
Contributor
Copy link

I've replaced a lot of occurrences of "agda" with "mikan" in HACKING.md,
and several instances of the original repository. The line length and
style has also been changed to be a bit more consistent. References to
make and stack w.r.t. building/testing mikan have been removed
whenever possible.

I've replaced a lot of occurrences of "agda" with "mikan" in HACKING.md, and several instances of the original repository. The line length and style has also been changed to be a bit more consistent. References to `make` and `stack` w.r.t. building/testing mikan have been removed whenever possible.
HACKING.md Outdated
@ -31,3 +34,2 @@
Running `cabal install`, `stack install`, or `make` from the repository root should build Agda,
assuming you set up dependencies correctly (see "Troubleshooting Cabal").
Running `cabal build`, from the repository root should build Mikan, assuming
Owner
Copy link

remove first comma

remove first comma
pounce marked this conversation as resolved
HACKING.md Outdated
@ -34,0 +35,4 @@
Running `cabal build`, from the repository root should build Mikan, assuming
you set up dependencies correctly (see "Troubleshooting Cabal").
Note: you can speed up `cabal` builds at the cost of using more ram with
Owner
Copy link

RAM

RAM
pounce marked this conversation as resolved
pounce force-pushed update-hacking from 778c581f8d
Some checks are pending
ci/woodpecker/pr/test Pipeline is pending approval
to e6e8eda236
Some checks are pending
ci/woodpecker/pr/test Pipeline is pending approval
2026年04月26日 18:52:18 +02:00 Compare
ncf approved these changes 2026年04月26日 18:54:59 +02:00
chore: update woodpecker instructions
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
a8f9b20ce9 
Co-authored-by: Naïm Camille Favier <n@monade.li>
Sign in to join this conversation.
No reviewers
ncf
Labels
Clear labels
1 - scope
language
 Backwards-compatible changes to the surface language, such as adding new features.
1 - scope
language change
 Breaking changes to a documented part of the surface language. These should be documented and specifically called out in the changelog.
1 - scope
performance
 Semantics-preserving performance work.
1 - scope
task
 Changes that are not apparent to the user, e.g. developer documentation and refactors, which do not need to be documented.
A: dead-code
Dead code elimination and --save-metas.
A: errors
Reporting of error and warning messages.
A: highlighting
Highlighting during interaction & literate compilation
A: imports
Handling of imports and interface file de/serialization.
A: infra
Iinfrastructure (e.g. CI, developer documentation, the build system, or the repository itself)
A: instance
Instance declarations, arguments, and resolution
A: lhs
LHS checking, coverage checking, and clause compilation
A: modules
Declaration and instantiation of parametrised modules.
A: parallel
Parallel typechecking.
A: positivity
Positivity checking
A: printing
Pretty-printing, display forms, and the wording of diagnostic messages
A: records
Record declarations, record expressions and copattern matching
A: scoping
Scope checking (ConcreteToAbstract)
A: termination
Termination checking
0 - type
bug
 Issues describing an incorrect behaviour in the project, typos in the documentation, etc.
0 - type
discussion
 An issue raised to gather opinions on a proposed change, or a suggested language change.
0 - type
question
 An issue raised to ask a question.
9 - status
duplicate
 This issue or pull request already exists.
9 - status
info needed
 More information is needed from the submitter to decide how to proceed with the issue report.
9 - status
invalid
 The issue report or pull request does not describe an actual bug, or does otherwise does not meet the contributing guidelines.
good first issue
Interested in contributing? Get started here.
upstream
Related to an upstream repository, already reported there
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
1lab/mikan!47
Reference in a new issue
1lab/mikan
No description provided.
Delete branch "pounce/mikan:update-hacking"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?