kvid

- We need to apply such a change ASAP to avoid the GitHub Actions error for each push to the PR branch, that I experience now: "_This request has been...

@formatc1702 - Thank's for responding! > I have very limited experience with GH Actions, linters, etc. The same goes for me, I'm afraid (except isort & black). > but here...

This update of GitHub Actions has been merged into master. I also tried cherry-picking this commit to #416, and the new actions were executed successfully, but two old outdated actions...

@tobiasfalk wrote: > I do not know that much about github, but one solution could be to "archive" them. https://graphite.dev/guides/archive-git-branch Thank you for responding quickly! I've never used this archive...

This accepted answer seems relevant: https://stackoverflow.com/questions/67743583/how-can-i-stop-github-actions-from-requiring-old-nodejs-builds I find the old actions as required before merging into `dev` or `master`, and it seems I can remove them as required, but I...

@0x0fe wrote: > I am struggling to reproduce something like this, no problem with the conenctors, however i am really not sure how to generate the two wire studs (red...

@0x0fe wrote: > So this is the best i can do, i wish we could make X3 view less anbiguous, for example if it could be a little higher the...

I agree with @martinrieder that a more generic CLI optional argument is better than a very specialised one. Maybe we can think even wider to obtain a more complete functionality:...

> @kvid what you are suggesting is similar to [yamlpath](https://github.com/wwkimball/yamlpath). No need to reinvent the wheel... 😊 I don't know anything about `yamlpath` - I took a peek through your...

This seems to be a duplicate of #330. If you agree, please join that discussion, and close this issue as not planned. If not, then explain here what makes this...