Skip to content

Commit

Permalink
Avoid hardcoding the release directory to ../../.
Browse files Browse the repository at this point in the history
When preparing the list of assets to public
(RELEASE_ASSETS_AFTER_RELEASE), do not hardcode the release directory to
the top-level directory of the repository (../../, relatively to
src/ontology). Use the RELEASEDIR variable.

This concerns all assets, not only the mapping files.
  • Loading branch information
gouttegd committed Oct 31, 2024
1 parent a8853c5 commit 205e11c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion template/src/ontology/Makefile.jinja2
Original file line number Diff line number Diff line change
Expand Up @@ -1246,7 +1246,7 @@ public_release:
$(GITHUB_RELEASE_PYTHON) --release $(TAGNAME) $(RELEASEFILES)
{% else %}

RELEASE_ASSETS_AFTER_RELEASE=$(foreach n,$(RELEASE_ASSETS), ../../$(n)) $(foreach n,$(RELEASED_MAPPING_FILES), ../$(n))
RELEASE_ASSETS_AFTER_RELEASE=$(foreach n,$(RELEASE_ASSETS), $(RELEASEDIR)/$(n)) $(foreach n,$(RELEASED_MAPPINGS), $(RELEASEDIR)/mappings/$(n).sssom.tsv)
GHVERSION=v$(VERSION)

.PHONY: public_release
Expand Down

0 comments on commit 205e11c

Please sign in to comment.