בדוק גרסה ספציפית של פלאגין?

מפתח

סיכום מבוסס בינה מלאכותית

The discussion revolves around checking out a specific version of a plugin in Discourse using app.yml. codechef asks how to specify a particular commit hash for a plugin when rebuilding the app, as the default behavior pulls the latest version, causing compatibility issues. Falco suggests using git options like -b, but codechef notes that this doesn’t work with commit hashes directly. codechef eventually resolves the issue by forking the repository, creating a branch from the desired commit, and referencing it in app.yml. jimkleiber expresses interest in a more streamlined solution, such as an

1

Is there a way, inside of app.yml, to make rebuild checkout a specific version of a plugin?

I’m working on an older branch than master. When I ./launcher rebuild app it pulls the latest version of a plugin that I don’t control. The latest version of that plugin isn’t compatible with the older version of discourse. This causes the build to fail in my test environment.

Ideally, I’m thinking something like the following in app.yml with the other plugins:

- git clone https:/github.com/path/to/plugin.git?commit=ec64234359282

I’m open to alternative solutions. Just need discourse to build with that version of the plugin.

2

You can use standard git options for that, like the -b flag.

3

Unfortunately, the plugin doesn’t provide a named branch for the version I’m after. I’m trying to pull a specific revision (commit hash) from master. It doesn’t appear that -b works with commit hashes.

From the command line, I can git clone then git checkout to get what I need. Is there a ways to do that in app.yml?

4

Okay, @Falco 's solution worked, but I had to go about it in a round about way.

  1. I forked the original repo
  2. Cloned it locally on my dev machine
  3. Created my branch from the desired commit
    • git branch foo ec64ae8
  4. Pushed that branch to my github
    • git push -u origin foo
  5. Updated my app.yml with
    • git clone -b foo git@github.com:my-repo.git

Seems like there should be an easier way, but this gets the job done. Thanks for the direction @Falco !

5

Yeah, I’m testing out new plugins, especially the chat plugin, and noticed that it seemed to have broken on my site and am wondering how to just roll back to the previously installed version or even to manually type in the commit version I’d like.

I imagine going forward I’d love to see this in the upgrade dashboard, something like the “undo” button for upgrade, but for now, I’m hoping there could at least be a faster way than what seems to be a more brute-force effort you did to workaround it.