issue_comments
7 rows where author_association = "CONTRIBUTOR" and user = 51911758 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- remigathoni · 7 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1498639992 | https://github.com/pydata/xarray/pull/7669#issuecomment-1498639992 | https://api.github.com/repos/pydata/xarray/issues/7669 | IC_kwDOAMm_X85ZU254 | remigathoni 51911758 | 2023-04-06T07:53:56Z | 2023-04-06T07:53:56Z | CONTRIBUTOR |
I'll fix it! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Docstrings examples for string methods 1639361476 | |
| 1492349784 | https://github.com/pydata/xarray/issues/4361#issuecomment-1492349784 | https://api.github.com/repos/pydata/xarray/issues/4361 | IC_kwDOAMm_X85Y83NY | remigathoni 51911758 | 2023-03-31T17:39:00Z | 2023-03-31T17:39:00Z | CONTRIBUTOR | An overview would make it easier to find sections for sure. Including what you've mentioned, here's what I have for the overview: OverviewProject Structure Prerequisites * Set up your development environment * Linux * Windows * Git workflow (Will link to an external resource) Code * Suggest a feature * Report a bug * Find an issue to work on * Set up the environment * Making changes * Create branch * Edit files * Documenting your changes * Testing * Writing tests * Running tests (for both the code and the docstrings where necessary ) * Commit your changes Links to the section that mentions pre-commit (and the pre-commit-ci bot) and commit message tags for controlling CI * Push to fork * Create a pull request * Automated tests * Backward Compatibility * Code standards and conventions Documentation * Suggest doc improvements * Find something to work on * Making small changes (e.g typo fixes) * Check existing GitHub issues * Propose a change * Set up the documentation environment * Ways to contribute to the documentation * User guide * Make changes * Build docs * Docstrings * Make changes * Docstrings format * How to write numpy style docstrings * Examples * Run doctests
PR best practices (Will link to short section on what to put into the PR description / title) I have tried to make the contribution workflow for the docs and code as separate as possible which I think makes it easier to follow. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
restructure the contributing guide 683142059 | |
| 1486694195 | https://github.com/pydata/xarray/pull/7674#issuecomment-1486694195 | https://api.github.com/repos/pydata/xarray/issues/7674 | IC_kwDOAMm_X85YnScz | remigathoni 51911758 | 2023-03-28T11:29:43Z | 2023-03-28T11:29:43Z | CONTRIBUTOR |
Thank you @dcherian ! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adjust sidebar font colors 1640260666 | |
| 1483139824 | https://github.com/pydata/xarray/pull/7669#issuecomment-1483139824 | https://api.github.com/repos/pydata/xarray/issues/7669 | IC_kwDOAMm_X85YZurw | remigathoni 51911758 | 2023-03-24T17:09:33Z | 2023-03-24T17:09:33Z | CONTRIBUTOR |
Thank you! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Docstrings examples for string methods 1639361476 | |
| 1477031884 | https://github.com/pydata/xarray/issues/4361#issuecomment-1477031884 | https://api.github.com/repos/pydata/xarray/issues/4361 | IC_kwDOAMm_X85YCbfM | remigathoni 51911758 | 2023-03-20T22:33:27Z | 2023-03-20T22:33:27Z | CONTRIBUTOR | @keewis What do you think of this structure? Structure for the Contribution GuideOverview
Ways to Contribute
How to Report a BugHow to Request an EnhancementSetting Up the Development EnvironmentBefore contributing to either the docs or the codebase, set up the dev environment. * Install Anaconda or miniconda * Fork the repository * Clone the repository Contribute to the CodebaseCode standards
How to contribute to the codebase
Contribute to the documentationDocumentation comprises of: * Docstrings - Add a numpy docstring guide * Docs in the xarray/doc folder - Uses rst How to contribute to the documentation
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
restructure the contributing guide 683142059 | |
| 1473706221 | https://github.com/pydata/xarray/pull/7625#issuecomment-1473706221 | https://api.github.com/repos/pydata/xarray/issues/7625 | IC_kwDOAMm_X85X1vjt | remigathoni 51911758 | 2023-03-17T11:41:01Z | 2023-03-17T11:41:01Z | CONTRIBUTOR |
Thank you @dcherian ! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Use more descriptive link texts 1623949333 | |
| 1466820667 | https://github.com/pydata/xarray/issues/7617#issuecomment-1466820667 | https://api.github.com/repos/pydata/xarray/issues/7617 | IC_kwDOAMm_X85Xbeg7 | remigathoni 51911758 | 2023-03-13T19:26:47Z | 2023-03-13T19:26:47Z | CONTRIBUTOR |
I'll open a PR thanks @TomNicholas ! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
The documentation contains some non-descriptive link texts. 1620573171 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] (
[html_url] TEXT,
[issue_url] TEXT,
[id] INTEGER PRIMARY KEY,
[node_id] TEXT,
[user] INTEGER REFERENCES [users]([id]),
[created_at] TEXT,
[updated_at] TEXT,
[author_association] TEXT,
[body] TEXT,
[reactions] TEXT,
[performed_via_github_app] TEXT,
[issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
ON [issue_comments] ([user]);
issue 5