Is hardis:work:refresh unsupported?

[readeral]

Currently this command trips up on

sfdx-hardis/src/commands/hardis/work/refresh.ts

Line 89 in d5922d4

if (config.get('EXPERIMENTAL', '') !== 'true') {

because config isn't a Map/is just a parsed object, doesn't have a get method - but also this line is trying to gate the method behind an experimental flag, so that suggests it was the start of an idea that hasn't really blossomed.

hardis:work:refresh uses forceSourcePush directly but looking at hardis:work:new, the approach is to use initOrgMetadatas (and other init methods) which themselves use forceSourcePush after changing SharingCalc etc. which seems a bit more resilient.

But then also refresh seems to be the only refreshing command that tries to include forceSourcePull. hardis:work:new obviously expects you to be starting something new and to have saved your prior work, so instructs you to run hardis:work:save first.

But anyway... that was all my understanding the different commands out loud... but I think there's still a place for hardis:work:refresh, it's just that it currently doesn't work. hardis:scratch:push requires you to do all the local source merging yourself, which is actually my preference, I just have a colleague who regularly gets tripped up and giving him a single command is so much easier 😅

[nvuillam]

@readeral I was very optimistic when I created the command... I wanted to offer to non technical users a way to merge the latest commit of the target branch in the current branch + update the org... but it's too clumsy , that's why i removed it from the menu ^^

[nvuillam]

If we wanted to make it work, we might call sfdx-git-delta to get the delta package.xml and deploy only this one ?

If you want to give a try updating this command, it would be great ^^

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment, or this will be closed in 7 days.