@lochipi I notice that you have set the preview link in this ticket.
Is this to indicate that you are ready for the editors to review/edit your article?

@lochipi I notice that you have set the preview link in this ticket.
Is this to indicate that you are ready for the editors to review/edit your article?

Hi @rlengland, I need to make a few adjustments, I will let you know by today when done.

Hi, it's now ready for review. Thanks

Thank you @lochipi

Thank you, also, for the featured image. Note, however, that we have a standard size for these images since they are shared by other sites.

I have rescaled the image to conform to the 1890x800 px size but as you can see it has changed the aspect ratio (squashed it vertically a bit). If this modified image is okay, then we can go with it. If not, feel free to modify it as you wish.

A note about replacing the existing image: I find that if the name of the image jpg file is the same as an existing one, it makes it difficult to add the image. I usually change the name slightly before adding it.

@rlengland, can you check again? I have added another one, which is much better now, quality.

@lochipi That image looks just fine. Thank you.

Wait, the github element on the far right - is it okay or I need to adjust to the end? fill the gap. I hope it's not an issue to upload as many images in the wordpress admin, I can't find a delete btn - if you do you can remove the existing ones,

@rlengland, I've updated it with the updated img

@rlengland, I've updated it with the updated img

The last one is good and I've removed the older versions Thanks.

Okay, thanks.

On Thu, May 22, 2025, 11:27 PM Richard England pagure@pagure.io wrote:

rlengland added a new comment to an issue you are following:
``

@rlengland, I've updated it with the updated img

The last one is good and I've removed the older versions Thanks.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-magazine-newsroom/issue/393

@lochipi In reviewing your article we believe there may need to be some further work.

You merge upstream/main into your local branch and then push the local branch back to origin/main. This will work, assuming the original clone is from a fork of the repository and not from the upstream repo. You don't demo the clone command, however..

At a minimum, you should show the git clone ... command before stating "This shows all remotes, both origin (your fork) and upstream (original project)".

It would be great if you show some sample output for commands like git remote -v as well. Perhaps you could generate some real output and then edit it substituting something like example.org, or something similar, as needed for your actual upstream repo.

@rlengland, the first idea was updating your fork in Pagure since we dont have an "sync your fork" there. That's where the first guide originated from, with sample snipets. Then I thought I could replicate it the same content and those still using or maybe are being blocked contributing can start now, but we're moving to Forgero soon, @glb and @augenauf suggested I make it general.

I haven't tried Forgero before, does it have a "sync your fork" feature? if so, do we really need this when I people can just click it and update their sync :)

... do we really need this when I people can just click it and update their sync :)

Showing how to do it with the CLI is fine, even if there are ways to do the same thing via the web interface. Some people might prefer to use the command line or their own file editor instead of the web interface.

... do we really need this when I people can just click it and update their sync :)

Showing how to do it with the CLI is fine, even if there are ways to do the same thing via the web interface. Some people might prefer to use the command line or their own file editor instead of the web interface.

yeap, got it. Will do it

@lochipi Checking in with you to see if this article is ready for another review.

@lochipi Checking in with you to see if this article is ready for another review.

Hi @rlengland, I'm quite busy with the internship, I would love some help on setting up forgero. There's a magazine article I am preparing as part of my internship, will drop it this week

@lochipi Any status update you can provide?

@lochipi Any status update you can provide?

Hi, sorry for leaving this hanging for a while. I got caught up and wasn’t sure what forge this was, which confused me. I’ll get back to it soon and should have it done by this week.

@lochipi I there a status update on your article?

@lochipi I there a status update on your article?

oh no! I haven't found time to get to this. I'll get to this in January. But I think for now we can stall it until I post an update.

I'll leave it "In progress". After all, it is still in progress :-)

@lochipi Is there a target date for this article?
Articles are currently tracked using Pagure which is scheduled to be retired in June of this year. We will need to know if this article should be carried over to the replacement tracking scheme on Discourse.

Thanks.

@lochipi I have opened a new ticket to track your article. It is currently in that stalled category in the new KanBan here:
https://discussion.fedoraproject.org/t/stay-up-to-date-with-upstream-using-git/193888/1

If you decide you no longer want to continue with this please let us know. Transferring ownership to tickets is currently not possible so it appears as though I own this issue. However, I will close this near the end of July if I hear nothing furhter.

Published?

Not published. Opened the following in the "Stalled" category since he
has at least part of the article in WP.  Just need to know that we was
ready for review etc.
https://discussion.fedoraproject.org/t/stay-up-to-date-with-upstream-using-git/193888

~~R
Non fenestras quia MCMXC - Linux vincit

On 6/15/26 12:38, Gregory Lee Bartholomew wrote:

glb added a new comment to an issue you are following:
Published?

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-magazine-newsroom/issue/393

But this old ticket on Pagure has a status of "Closed: Published". I was just suggesting that you move it to stalled here on Pagure as well.

Edit: Oh, I guess you deleted all the stalled tickets? That works too. :-)