Fix output folder

[askpatrickw]

This fix uses the output folder defined in the config file.

[askpatrickw]

But it is probably a breaking change for people...

[rehanhaider]

Would it not be better to parameterise the output folder? Something like

pelican ${PELICAN_CONTENT_FOLDER:=content} -o ${PELICAN_OUTPUT_FOLDER:=output} -s ${PELICAN_CONFIG_FILE:=publishconf.py}

After that we can add override paramets in action.yml. This will ensure people who are already using the action are not affected as well.

[rehanhaider]

Would it not be better to parameterise the output folder? Something like

pelican ${PELICAN_CONTENT_FOLDER:=content} -o ${PELICAN_OUTPUT_FOLDER:=output} -s ${PELICAN_CONFIG_FILE:=publishconf.py}

After that we can add override paramets in action.yml. This will ensure people who are already using the action are not affected as well.

Scratch that. I missed your comment about config file.

This will not be breaking change for existing users as the marketplace action is tagged to a particular version.