README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest.
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Subject
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Subject (what)
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Subject Body (what)
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Subject Body (what) (why)
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest.
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Fixed Added Updated Removed Refactored
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest.
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. 72 characters
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Space
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. Capitalization
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. 72 characters
README Received feedback that the README was hard to navigate. With a Table of Contents, people are able to quickly scan what the README provides and immediately jump to a topic of interest. actually basically furthermore however obviously of course ...etc...
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint
stu f f f i nished discussed work 8790d748e650 (Brooke Kuhlmann, 0 seconds ago): Did some stu f f Commit Body Leading Line Error. Use blank line between subject and body. Commit Body Paragraph Capitalization Error. Capitalize f i rst word. Line 2: " f i nished discussed work" Commit Subject Pre f i x Error. Use: /Fixed/, /Added/, /Updated/, /Removed/, /Refactored/. 1 commit inspected. 3 issues detected (0 warnings, 3 errors). https://www.alchemists.io/projects/git-lint