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
[DOC] add links and edit buttons to doc #3964
Conversation
👋 @Remi-Gau Thanks for creating a PR! Until this PR is ready for review, you can include the [WIP] tag in its title, or leave it as a github draft. Please make sure it is compliant with our contributing guidelines. In particular, be sure it checks the boxes listed below.
For new features:
For bug fixes:
We will review it as quick as possible, feel free to ping us with questions if needed. |
Codecov Report
@@ Coverage Diff @@
## main #3964 +/- ##
==========================================
+ Coverage 91.78% 91.79% +0.01%
==========================================
Files 134 134
Lines 15772 15772
Branches 3284 3284
==========================================
+ Hits 14476 14478 +2
+ Misses 752 751 -1
+ Partials 544 543 -1
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Nice ! |
We can also add mastodon https://fosstodon.org/@nilearn and discord too. The edit button will allow anyone to edit and directly commit to main? I'd prefer to always go through PRs if it's possible |
Failures seem unrelated; see main. I'll open a PR to fix |
Good idea. Will add those.
Technically the edit button is always there on the github interface, so we already have this problem. This edit button makes just easier to know what doc page cooresponds to what github document. If we set up our branch protection rules properly, this "commit to main" should be avoidable. Here is what it looks like on the BIDS specification. And on another repo where I set the rules so no direct commit to the default branch is possible. On our side we get no such warning. |
Ok I misunderstood the intention so thanks for clarifying.
Indeed |
what it would look like |
by the way I think we can also have twitter, discord and mastodon badge in the top of the readme |
Done |
Confirmed by me trying to do a manual edit. Thanks!! |
Looks good! Can you rebase on main? |
Avec plaisir. |
closes none