Closed tilk closed 1 week ago
Would it make sense to rebase transactron repository on top of something like git-filter-repo
(note: invocation is destructive!) with --path transactron/ --path test/transactron/ --path-rename test/transactron/:test/ --path coreblocks/transactions --replace-message <replace file with "#==>https://github.com/kuznia-rdzeni/coreblocks/pull/">
to keep easier to get history with valid PR references in one place?
Coreblocks README needs updating; and maybe docs/transactions.md should be preserved, but only with url to Transactron gh-pages docs?
Would it make sense to rebase transactron repository on top of something like
git-filter-repo
(note: invocation is destructive!) with--path transactron/ --path test/transactron/ --path-rename test/transactron/:test/ --path coreblocks/transactions --replace-message <replace file with "#==>https://github.com/kuznia-rdzeni/coreblocks/pull/">
to keep easier to get history with valid PR references in one place?
I just did that, but it unfortunately invalidated all active PRs in Transactron repo.
This PR finally extracts Transactron to external repo, https://github.com/kuznia-rdzeni/transactron. Depends on #754.
In the same time, the
amaranth-stubs
submodule is removed and replaced by an entry inrequirements.txt
. My reasons are:pyproject.toml
is used. I'd like to move Coreblocks topyproject.toml
- I already did that in transactron.amaranth-stubs
version needed to be installed usingpip
after each change anyway.