Skip to content

Docs/table of content #536

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

Closed

Conversation

kalio007
Copy link
Contributor

Added table of contents to contribution guide and fix typos.

@kalio007 kalio007 force-pushed the docs/table-of-content branch from 6171dc5 to e1069df Compare April 23, 2025 22:26
@kalio007
Copy link
Contributor Author

Hello @umegbewe
Please check this out.

@umegbewe
Copy link
Contributor

@kalio007, thanks for adding the table of contents and fixing the typos

I noticed the branch currently contains commits that are already in main but have new SHAs. That usually happens when the branch was created from an older copy of main and then rebased.

Rebase the branch onto the latest main, or

git reset --hard upstream/main and re-apply only your table-of-contents changes,

Then git push --force-with-lease to update the PR.

That will leave the PR with just your relevant changes and keep the history tidy. Once that’s done, I'm happy to merge

@kalio007 kalio007 closed this Apr 24, 2025
@kalio007 kalio007 force-pushed the docs/table-of-content branch from e1069df to 31324ff Compare April 24, 2025 11:36
@kalio007
Copy link
Contributor Author

Hello @umegbewe
Although the PR closed, but I have added the changes alone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants