-
Vibe.d seems promising, but I would like to know if there are any real-life applications created with it (except for the vibe.d's website)? Please, do not suggest the examples, but real world applicat…
-
This is rather a question whether this might be feasible to improve the overall process: Is it possible that the bot watches for commits in the language repositories and creates a new commit to update…
-
## deadalnix (deadalnix) reported this on 2023-06-13T12:56:46Z
### Transfered from https://issues.dlang.org/show_bug.cgi?id=23989
### CC List
* alphaglosined
* dlang-bugzilla (CyberShadow)
* maxhat…
-
## deadalnix (deadalnix) reported this on 2023-06-13T12:56:46Z
### Transfered from https://issues.dlang.org/show_bug.cgi?id=23989
### CC List
* alphaglosined
* dlang-bugzilla (CyberShadow)
* maxhat…
-
Currently when a release is made, it's tagged as "Latest release", e.g. https://github.com/dlang/dub/releases/tag/v1.12.0-beta.1
This cause all tools using the latest release to start using the bet…
-
I am usually working on OSX those days, and when it comes to Linux, tend to use Alpine Linux because a container is quite easy to start. However, running `dub test -- --single --trace` (or even withou…
-
It's a waste of precious resources:
![image](https://user-images.githubusercontent.com/4370550/34644295-0fc0ac4a-f334-11e7-8870-15d0da009e31.png)
-
The bot could add the auto-merge label for full automation.
The diff is trivial always anyways and if it fails on the CI, the PR won't be merged.
-
The idea is simple: old PRs require a lot of manual pinging and if the author is gone, it usually ends up being closed after a couple of pings.
The bot could do the following:
- if a PR has had n…
-
At the moment, we frequently hit the following issue:
- Buildkite builds a project
- Some change is made in the project (e.g. in `.travis.yml`)
- Nothing happens for a while
- A new release is tag…