Skip to content
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

Wrong placement of _index.md file #1196

Closed
yiannisbot opened this issue Oct 6, 2020 · 0 comments · Fixed by #1203
Closed

Wrong placement of _index.md file #1196

yiannisbot opened this issue Oct 6, 2020 · 0 comments · Fixed by #1203
Assignees
Labels
hint: active Hint: Tasks currently in an active project scope: tooling Scope: web rendering, build system, CI and other tooling type: bug Type: bug in the current code

Comments

@yiannisbot
Copy link
Collaborator

yiannisbot commented Oct 6, 2020

The _index.md file in this path/folder: https://github.com/filecoin-project/specs/blob/master/content/systems/filecoin_mining/storage_mining/mining_cycle/ gets the wrong position in the ToC and text. It becomes a subsubsection of the previous subsection, instead of becoming a subsection itself. All the frontmatter is the same as in all other cases, so I don't know how to make it become section 2.6.2.4, instead of 2.6.2.3.3.- or perhaps I'm missing something?

Screenshot 2020-10-06 at 21 55 54

@hugomrdias @olizilla any hints on whether I'm doing something wrong, or there is a bug?

@yiannisbot yiannisbot added hint: active Hint: Tasks currently in an active project scope: tooling Scope: web rendering, build system, CI and other tooling type: bug Type: bug in the current code labels Oct 6, 2020
hugomrdias added a commit that referenced this issue Oct 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hint: active Hint: Tasks currently in an active project scope: tooling Scope: web rendering, build system, CI and other tooling type: bug Type: bug in the current code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants