👍 Voting for Issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation
Research direction
This is a permanently pinned GitHub issue explaining how to vote with 👍 reactions and subscribe for updates. Start by reviewing the issue text and the linked voted issues documentation at scitools-iris.readthedocs.io/en/latest/voted_issues.html. No specific file, test, or documentation change is requested, so the definition of done is not established.
Written by the indexing model from the issue text.
Description
👍 Voting for Issues
This is a permanently pinned issue dedicated to all users and contributors of Iris.
We the core developers of Iris focus on the core aspects that we think are needed by our community but we also need help in prioritising some issues that mean the most to you. To enable this we will use a the 👍 reaction on any issue header to signify a vote.
If you have a specific question please raise an issue .
How to Vote?
- Give a 👍 to any issue header (not the subsequent comments) to indicate your vote on any issue.
How to ensure I am updated?
We suggest you subscribe to the issue so you will be updated. When viewing the issue there is a Notifications section where you can select to subscribe.
Where can I see the voted issues?
Currently the GitHub web interface only allows for sorting by the number of reactions in the issue header and all subsequent comments. This is not a clear indication on voting, only that is has an active comments. For a clear list please see the voted issues section of our documentation.
- Dominant language
- Python
- Stars
- 724
- Forks
- 317
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SciTools/iris
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100