How to fork when self-hosting?

[matenauta]

Hi there, can we use something like that?

TryGhost/actions/blob/main/.github/workflows/custom.yml

What we need to change if that file is OK?

I want to update some strings that I edited manually on my fork of Ghost (I keep the repo merged).

Thanks.

[markstos]

That workflow file runs npm pack on a branch, resulting in a .tgz file of the project.

Because JavaScript, HTML and CSS are not compiled there’s not normally a need to run this step on a fork.

Also, ghost install installs .zip files, and this workflow generates a .tgz file. It’s not even clear that it generates something that be installed directly.

If you want to maintain some differences, I recommend you create a file in the “unified diff” file format and save it as a .diff or .patch file.

Then after you run the standard upgrade process, run something like patch <my-patch.diff to patch the code with your differences.

[vikaspotluri123]

@markstos

Also, ghost install installs .zip files, and this workflow generates a .tgz file. It’s not even clear that it generates something that be installed directly.

Ghost CLI added support for installing from a tgz back in August: Release 1.22.0 · TryGhost/Ghost-CLI · GitHub

[matenauta]

OK I don’t really understand how to use Actions but I think I can use old school method:

# Rename origin to upstream again
git remote rename origin upstream

# Add your fork as an origin, editing in <YourUsername>!
git remote add origin git@github.com:<YourUsername>/repo

Is that correct?

[markstos]

That syntax adds your repo as git’s origin repo, but to understand if that will help you, you need to post the whole solution you are trying.

[matenauta]

I wonder if can I change the origin and then pull my own repo to keep Ghost forked?

(I understand that I need to mantain my own fork and keep it updated)

[markstos]

Yes, it looks like you’ve got a Github Actions workflow that supports custom branches and you also have a custom branch.

I work with Github Actions a lot at work and it can be a tool that can be complex to work with at times.

Here I described a lower-tech way to maintain a fork that might be a good fit if you have a small number of changes:

Is there any way we can modify the cookie name for "ghost-members-ssr"

Are you familiar with creating patch files? You could do something like this: Before you patch the file, create a .bak of the unmodified version. Let’s say now you have file.js.bak and file.js. Generate a patch file: diff -u file.js.bak file.js>my-changes.patch. Except, run this command at the root of the project. Create a small script which wraps ghost update and then applies your patch: #!/bin/sh ghost update patch -p1 <my-changes.patch Now each time you upgrade Ghost, your patch will be r…

[matenauta]

We need to force-update language on e-mails. There are changes on 9 files but if I get how to fork and keep Ghost updated, I will edit more.

Then I will try to do PRs on main but I don’t have 1/10 level you have folks, sincerelly

Thanks, I’ll try to get how to engage Github Actions with our fork.