You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out by @FabioPinheiro in #64 (comment), a recent merged PR updating the did:peer:2 spec should have updated the github pages. However, the built artifact from the action still has the old spec contents.
The text was updated successfully, but these errors were encountered:
Pretty sure it’s because the main branch is still master in the repo, and the action triggers on main. Changing the name of the branch to see if that fixes it. Might take a tweek PR to trigger the build.
The GitHub Action was triggered based on a merge into main, so I changed that to master. I don’t have the power to change the branch name to main, but we should do that — and change the GHA to trigger on main.
Once executed, the GHA was pushing the file to the gh-pages branch (yay!), but GH Pages settings published from the master branch. I updated the source of the Pages to be the gh-pages branch.
As pointed out by @FabioPinheiro in #64 (comment), a recent merged PR updating the did:peer:2 spec should have updated the github pages. However, the built artifact from the action still has the old spec contents.
The text was updated successfully, but these errors were encountered: