tison
https://github.com/korandoru/hawkeye/blob/v5.1.0/release.py @epage Currently I wrap the logic in a simple script. The logic is almost file content replacement. Another issue is that the replacement/hook search path is always from package...
The original motivation vanished because I change `image: ...[{{version}}|latest]` to `image: Dockerfile`. But this issue may be still relevant. UPDATE - No. Pull is much faster and build in place.
@lhotari do we do version upgrade for test-infra's dependencies?
This can be more tricky than it seems to be. Because we cannot (or should not) use the filesystem creation and last modified day but the day from CVS (Git...
I can help in this issue, as long as you set up the token for cargo publish. Here is how we did it for Apache OpenDAL: https://github.com/apache/opendal/blob/5e735cc53cd8638f47bd10b67d5d6e258ff22b67/.github/workflows/release_rust.yml#L69-L84 Mainly, it's: ```...
> 他的 body 列是复用的，也就是说无论是 issue、PR、comment、review comment，内容都是存在 body 列，这可以大幅减少冗余，但每行的数据是不完整的，如果要做内容分析，就需要提取多行的数据。但其实这也是可以接受的，虽然使用上会较困难，但数据存储的压力很小。 为什么说每行数据是不完整的呢？ BTW 这种交流方式似乎 Discussions 的 Thread 会舒服一点..
``` $docker image inspect cgr.dev/chainguard/graalvm-native --format='{{.Size}}' 75360713 ```
For my use case, I may want only an API to get the current pressed key ..