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
The current system of updating morebits docs (added in #1190) appears to be a mess. All the configs are in gh-pages branch. But the code is in master. The easy thing to do would be to just copy paste the code into gh-pages branch then run the update command. But the commit history suggests this isn't the way it was being updated. Looks like rebases were being done to update the code in gh-pages branches.
I think ideally we should have a way to keep the docs config in the master branch and generate docs from there, but then commit it into the gh-pages branch. A github workflow could help with this, c.f. twinkle-core's workflow for automatically building i18n messages from master branch and committing it to another branch.
The text was updated successfully, but these errors were encountered:
The current system of updating morebits docs (added in #1190) appears to be a mess. All the configs are in gh-pages branch. But the code is in master. The easy thing to do would be to just copy paste the code into gh-pages branch then run the update command. But the commit history suggests this isn't the way it was being updated. Looks like rebases were being done to update the code in gh-pages branches.
I think ideally we should have a way to keep the docs config in the master branch and generate docs from there, but then commit it into the gh-pages branch. A github workflow could help with this, c.f. twinkle-core's workflow for automatically building i18n messages from master branch and committing it to another branch.
The text was updated successfully, but these errors were encountered: