fishworks / fish-food Goto Github PK

Raising a PR for this!

jq keeps reinstalling. Could this be due to the lack of traditional semver (1.6 vs. 1.6.0)?

when I use GoFish install jcli plugin on windows 10 environment:
PS C:\WINDOWS\system32> gofish.exe init
The following new directories will be created:
C:\ProgramData\Fish
C:\ProgramData\Fish\Barrel
C:\ProgramData\Fish\Rigs
C:\ProgramData\bin
C:\Users\SyJun\AppData\Local\Fish
==> Installing default fish food...
Error: Unable to get repository: Cloning into 'C:\ProgramData\Fish\Rigs\github.com\fishworks\fish-food'...
fatal: Invalid path '/cygdrive/c/WINDOWS/system32/C:\ProgramData\Fish\Rigs\github.com\fishworks\fish-food': No such file or directory
: exit status 128
PS C:\WINDOWS\system32> gofish.exe update
==> Rigs updated!
NAME

🐠 rigs updated in 1.0011ms
PS C:\WINDOWS\system32> gofish install jcli
Error: no fish food with the name 'jcli' was found

While I am much supportive of (and very happy with) the automated distribution of the goods we produce, the behavior of the bot to copy and paste the release notes including @<username> mentions creates a lot of noise in my already hard to track notifications.

It would therefore be awesome if the bot could detect and modify username mentions, so that I no longer receive pings for something that is out of my hands.

The best way to do this at present is described in: github/markup#1168 (comment)

Wondering if gofish can also update apps or Just libraries

For example on Mac Apps and a .app, with the library inside.
On windows Apps have a manifest. For example for golang people use alot of the tools here: https://github.com/tadvi/winc

draft appears to be deprecated and archived. Should we remove it?

Right now the Github Actions CI only tests against a Linux install. This allows PRs that work for Linux to pass, but maybe issues like #1122 to arise with other platforms.

Should we tests against the other platforms? Future CI could look like:

1. step: gofish lint
2. if 1. passes, matrix gofish install on all platforms

This would make all builds longer, and requires the downloading of assets twice (once for the lint step, again for the install step -- this could be fixed with asset caching), but would ensure that all platforms have installable binaries.

https://github.com/wercker/stern

I would propose reimplementing the Circle CI tests on PRs, so that only the foods that has been changed is tested.
This could help us in actually identifying which PRs are good and which are bad.

If we still want to validate all foods on a regular basis this could be done with a weekly report/alert?

Looks like the squashctl team might've re-uploaded a new version of squashctl which broke existing shasums, as the binaries have changed. @scranton, would you mind taking a look into this?

See https://circleci.com/gh/fishworks/fish-food/440 for context.

cc'ing @clakeb - looks like the fish food for keptn is quite out of date.

https://github.com/keptn/keptn/releases

WASM to OCI doesn't have a release, only prereleases. It doesn't appear to be stable software. Does it belong here?

https://github.com/engineerd/wasm-to-oci

Hi,

I have started developing a bot that can create pull-requests when existing fish food gets new releases.

For now it is still quite simple and rough around the edges.
I will make the code open-source, when i have added a few safe guards.
It still needs to learn to only create pull requests for new releases, and not open multiple PRs for the same package/release multiple times.. ;)

https://github.com/gofish-bot

So this is just a heads-up that GoFish-bot will start trying to be an active contributor to the fish-food repo. 😄 🤖

Raising a PR for this too

See https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh

Raising a PR for this !

I will raise a PR for this 😄

Raising a PR for this!

https://github.com/junegunn/fzf

scoop: https://github.com/lukesampson/scoop

I will raise a PR for this

Raising a PR for this!

the main project has moved over to github actions. The same should be done here

https://github.com/roboll/helmfile

There's currently a problem in upgrading the linkerd food.

The problem seems to be that the version, that Linkerd published, does not follow Semantic Versioning.

$ gofish update && gofish upgrade
==> Rigs updated!
NAME                          
github.com/fishworks/fish-food

🐠  rigs updated in 6.333312243s
==> Rigs updated!
NAME                          
github.com/fishworks/fish-food

🐠  rigs updated in 2.458226787s
==> Upgrading buffalo...
🐠  buffalo 0.16.10: upgraded in 32.57126ms
Error: Error parsing version: Invalid Semantic Version

I see a couple of problems here that I think should be addressed:

• Linkerd food is broken.
• It is not possible to identify from the error message which food is actually the problem.
• The Linkerd lints and installs fine, but does not work when upgrading.

I can create a new PR with a better version, but I think that this may also require some cleanup on machines where the Linkerd Food is installed?

https://github.com/fission/fission/

I can raise a PR for this, if it's accepted!

I recently created a new tool called uff - update fish food. It's a small and bit hacky tool to update a gofish food that I used to raise some PRs recently.

Anyone can use the tool to update the fish food with ease, in most cases. So I thought may be we can mention it in the readme so that if anyone wants to raise a PR it's just very easy and automated too

https://github.com/gohugoio/hugo/releases/tag/v0.58.0

I'll raise a PR for this!

We need a way to inject the desired version into the install script.

url = "https://github.com/jenkins-zh/jenkins-cli/releases/download/v" .. version .. "/" .. name .. "-window-386.tar.gz",
->
url = "https://github.com/jenkins-zh/jenkins-cli/releases/download/v" .. version .. "/" .. name .. "-windows-386.tar.gz",

Raising a PR for this using uff 😁

I will raise a PR for the same 😄 And I am also changing the download url to https://get.helm.sh