Skip to content

Conversation

sebbASF
Copy link
Contributor

@sebbASF sebbASF commented Jun 27, 2024

build-cmark.sh builds code in a temp dir and copies output to desired location, so there is no need to parse stdout from build-cmark.sh to find the library

build-cmark.sh builds code in a temp dir and copies output
to desired location, so there is no need to parse stdout from build-cmark.sh to find the library
@gstein
Copy link
Member

gstein commented Jun 27, 2024

+1 on the concept, and initial review looks good.

# ensure LIBCMARKDIR is defined for subsequent steps
echo "LIBCMARKDIR=${LIBCMARKDIR}" >> $GITHUB_ENV
# build the code and define LIBCMARKDIR under $WORKDIR
bash ${{ github.action_path }}/build-cmark.sh $GFM_VERSION $LIBCMARKDIR
Copy link

@jsoref jsoref Feb 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a $GITHUB_ACTION_PATH which you should generally use (and you should never use ${{ ... }} inside a run: block)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants