-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiki-Ops #2294
Comments
I know it's quite early but removing the old |
Readme says master is also pushed to IPFS by github actions but this doesn't seem correct. Should we add a new action to push new masters to IPFS? |
There's no CircleCI workflows that still run behind the scenes, right? |
don't think so (no .circleci folder), also couldn't find a login for it. |
|
Brief update:
|
I don't think there is any benefit of sustaining v1 as a separate branch as it just overcomplicates every
i. what is the point of having @emresurmeli @DrW3RK can I get your input as well? |
|
Cool we are on the same page. This was my point; we shouldn't touch v1 or move it out of master until we go to delete it, otherwise if do anything special with it (like removing it from master and keeping it in another branch or anything), and we need to do use it, we can't easily rebase it, we have to deal with all the CICD related overhead to make v1 run and then any structural changes (like doc and config stuff) that would need to get fixed manually |
You're right. Also realized the wikiops branch idea and trying to outpace updates to master isn't a good idea haha. The motive behind it was to "clean up" the repo, but also because as right now, both versions are submerged together - for instance, updating the README to specify "polkadot2" and "kusama2" instead of "polkadot" and "kusama", respectively, because of both being accounted for in the package.json, doesn't seem reasonable |
@DannyS03 I agree that naming should be consistant; what do you say we swap out |
That sounds good. Right those should only be the things to update |
Folder structure should be prioritized: #2415 (comment) |
@nam-hle #2442 (comment), any suggestions would be much appreciated |
@nam-hle it seems like injections still aren't getting recognized, for instance: https://wiki.polkadot.network/docs/learn-identity |
Hi @DannyS03, as I said before, the Markdown parser misunderstood between our variable underscore and italic one. It can be fixed easily by changing italic underscore to asterisk. But I suggest to use camel convention for our variable to fix the issue permanently. What do you think? |
It seems like we've tackled the immediate tasks related to "wikiops" up until this point, where IPFS related tasks has an issue of its own that is tracking progress. Because of recent updates we have encountered redirect conflicts (being warnings more than anything), which is also tracked by more than one issue at the moment. |
Workflows
Substrate version check: Substrate version check does not seem to be updating the links #1815Resolved in: update all rustdoc links to point to latest version #2330[x] Fix Prettier[ ] Run Prettier on external PRs: Make the prettier bot work on external PRs #944Usingpretty-quick
instead[ ] Abstract stalecheck: Abstract away the stale-check Github Action so others can use it #1064should also have a stale checker for older issues along with current stale checker for docs, and check for duplicate issues before creating an issue.-> instead of this updating in this manner, issues can be managed using a kanban board (ZenHub
has been setup, can add with https://www.zenhub.com/extension).Version 2
team attempts thus far:
Suggestions
learn
has learn guides,build
has build guides, etc.)[ ] Doc images could use a name convention and also organized into better sub-directories.I would say this can be revisited, but perhaps not a priority atm.Feel free to add/edit/refute and discuss these points.
The text was updated successfully, but these errors were encountered: