fix: ci: added referer to GOE post in release workflow

forge-ext / forge

Forge - Tiling and Window Manager for Gnome-Shell

GNU General Public License v3.0

838 stars 41 forks source link

Closed juarezr closed 1 month ago

juarezr commented 2 months ago

juarezr commented 2 months ago

Work in progress...

jmmaranan commented 2 months ago

I am curious if the upload really works. I am ready to pass the EGO account if this works.

juarezr commented 2 months ago

I am curious if the upload really works. I am ready to pass the EGO account if this works.

@jmmaranan

The code in the last commit worked on my computer.
Maybe something remains and that could manifest while running the workflow, but we are going to know just trying.
But before running, you must create 2 secrets in this git repository:
- GOE_USERNAME
- GOE_PASSWORD

jmmaranan commented 2 months ago

* But before running, you must create 2 secrets in this git repository:

  * GOE_USERNAME
  * GOE_PASSWORD

I have added the secrets.

juarezr commented 2 months ago

* But before running, you must create 2 secrets in this git repository:

  * GOE_USERNAME
  * GOE_PASSWORD

I have added the secrets.

PR's or commits will not trigger the release workflow.
But it is possible to test it by triggering:
- Manually starting it in the Actions tab
- Issuing a release in the release in Releases
- If you'd prefer to take a little extra caution, you can put a fake password and check if the password leaks in the logs of the action page. Locally I haven't found any leakage.

jmmaranan commented 1 month ago

@juarezr - I have to disable the release to GOE for now. I might bring it back before the next release