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
A common use case seems like it would be skipping to the first TOC marker. It would be nice if instead of having the end user have to increment the SKIP_LINE number if we could specify a special value (like -1) to automatically skip to after the first TOC marker. You could even parameterize this so that (-2) represented the second marker and so on. It seems like it would be a useful utility that would prevent people from having to edit the args for the pre-commit hook anytime text above the TOC (like badges, project descriptions etc..) are updated.
The text was updated successfully, but these errors were encountered:
A common use case seems like it would be skipping to the first TOC marker. It would be nice if instead of having the end user have to increment the SKIP_LINE number if we could specify a special value (like -1) to automatically skip to after the first TOC marker. You could even parameterize this so that (-2) represented the second marker and so on. It seems like it would be a useful utility that would prevent people from having to edit the args for the pre-commit hook anytime text above the TOC (like badges, project descriptions etc..) are updated.
The text was updated successfully, but these errors were encountered: