Git First Timers

There are lots of people that need help and want to make our community of software development open and inclusive.

This list displays the top 100 Open Issues with the 'first-timers-only' tag on Github.com.

That means this is a curated list of some of the best, most open, open source projects on the internet!

1 Add Button that will save image

Find it on GitHub

User can process image with few options available to choose from GUI created in FXML file.

Add Button (in specified FXML file) that will be responsible for saving processed image to file. After it, implement feature that will enable user to do so. Here is "TODO" comment that will help: code.

It would be nice to attach (in comment under this issue) screenshot that shows modified GUI.

2 create run.py file

Find it on GitHub

instead of if name equals main in main.py, create a new run.py file that imports from main.py and runs the bot

3 setup sphinx

Find it on GitHub

write appropriate comments in main.py and use sphinx to generate docs

4 cy.writeFile() is working with JS specs, but not with TypeScript specs

Find it on GitHub

This is in reference to the issue - https://github.com/cypress-io/cypress/issues/4456

Current behavior:

cy.writeFile("../output/oozie_workflows.csv", oozieId + ",False", { encoding: 'utf-8' flag: "a" });

The above code works fine with JavaScript specs, but with TypeScript specs - it throws below error message.

Argument of type '{ encoding: string; flag: string; }' is not assignable to parameter of type 'Encodings'. Type '{ encoding: string; flag: string; }' is not assignable to type '"utf-16le"'.ts(2345)

I'm sure this something to do with the file: index.d.ts. Please check.

Versions

Cypress - 3.3.1

5 make mail plugin use configparser

Find it on GitHub

you have to

  • make this plugin https://github.com/pyhoneybot/honeybot/blob/master/honeybot/plugins/mail.py use configparser
  • modify email.cfg from port:587 to port=587

6 On cy.visit('file://...) throw err to explain they should visit relative html file

Find it on GitHub

Current behavior:

We've had a couple people try to cy.visit('file://...). We support visiting .html files by specifying the relative path.

  • https://github.com/cypress-io/cypress/issues/4450
  • https://github.com/cypress-io/cypress/pull/4293

Desired behavior:

We can see if the user has passed in a file:// and throw a specific error advising them to pass in the relative path to the file from their projectRoot.

Versions

Cypress 3.3.1

7 Add chat-in-different-ways badge to README

Find it on GitHub

First Time?

This is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you πŸ’

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

The problem

We want to add a new badge to the README file:

![Join the chat at https://publiclab.org/chat](https://img.shields.io/badge/chat-in%20different%20ways-blue.svg)

Solution

At the top of the README, where you'll find other badges, lets add the following line:

[![Join the chat at https://publiclab.org/chat](https://img.shields.io/badge/chat-in%20different%20ways-blue.svg)](https://publiclab.org/chat)

Thanks!!

Step by Step

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

Please keep us updated

πŸ’¬β° - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

πŸ’¬ Get help

If you need any help - here are some options:

  • Comment below
  • Join our gitter chat at https://gitter.im/publiclab/publiclab

8 Add first-timers-only-friendly badge to README

Find it on GitHub

First Time?

This is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you πŸ’

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

The problem

We want to add a new badge to the README file:

![first-timers-only-friendly](http://img.shields.io/badge/first--timers--only-friendly-blue.svg?style=flat-square)

Solution

At the top of the README, where you'll find other badges, lets add the following line:

[![first-timers-only-friendly](http://img.shields.io/badge/first--timers--only-friendly-blue.svg?style=flat-square)](https://code.publiclab.org#r=all)

Thanks!!

Step by Step

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

Please keep us updated

πŸ’¬β° - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

πŸ’¬ Get help

If you need any help - here are some options:

  • Comment below
  • Join our gitter chat at https://gitter.im/publiclab/publiclab

9 Change colour for the featured tags on /questions page

Find it on GitHub

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you πŸ’

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

  • [ ] πŸ“ Update: The featured tags on https://publiclab.org/questions are not showing up. Update apps/views/questions/index.html.erb in the plots2 repository. Add color style to the feature imported in L-12 to L-16

![Screen Shot 2019-06-11 at 1 31 17 AM](https://user-images.githubusercontent.com/35326753/59223274-240d4100-8be9-11e9-8f73-870724606249.png)

  • [ ] πŸ’Ύ Commit your changes

    • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

10 Remove redundant function from community-toolbox.js

Find it on GitHub

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you πŸ’

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

  • [ ] πŸ“ Update the file community-toolbox.js in the community-toolbox repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

CHANGES

  • In src/scripts/community-toolbox.js,

diff $DIFF - function displayIssuesForRepo(org, repo, label, selector) { - toolbox.api.Issues - .getIssuesForRepo(org, repo, { qs: { labels: label } }) - .then(function onGotIssues(issues) { - issues.forEach(function(issue) { - toolbox.issuesUI.insertIssue(issue, selector); - }); - }); - }

After doing these changes, run grunt build before making a commit

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

πŸ”—- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

πŸ‘₯- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

πŸ€”β“ Questions?

Leave a comment below!

11 Add contributors hof

Find it on GitHub

Add contributors hall of fame similar to upstreamit

12 Add badges

Find it on GitHub

Add badges similar to flip-remote

13 Cypress.dom.isDetached missing from Typescript types

Find it on GitHub

Current behavior:

The method Cypress.dom.isDetached() type errors in Typescript projects.

Desired behavior:

The method Cypress.dom.isDetached() does not type error in Typescript projects.

Steps to reproduce: (app code and test code)

  1. Set up a Typescript Cypress project as described in https://docs.cypress.io/guides/tooling/typescript-support.html
  2. Write the following test:

```Typescript describe('Demonstrates bug', function() { beforeEach(() => { cy.setup(); });

it('demonstrates Typescript error'), function() { cy.get('button').then(($el) => { Cypress.dom.isDetached($el) }); }); }); 3. Get the following error: Property 'isDetached' does not exist on type '{ isHidden(element: HTMLElement | JQuery): boolean; }' ```

Versions

Cypress 3.2.0 Typescript 3.4.5 Chrome 74.0.3729.169 macOS 10.14.5

14 Issue template

Find it on GitHub

Please if you got any issue follow this template:

========

Purpose: Name of your purpose or proposal. Example: Compliance with ECMA 262

Feature: feature (existing or new) that you want to affect with this issue. Examples are: Nested components stack, dynamic components load. Dynamic complex cache control, etc.

Artifact: The artifact that you are affecting, touching , involving with this issue . Examples: Component Tag, Component Class, Controller, View, Effect, Import, Export, global scope... etc

Priority: how concerned are you about this issue: High priority, low priority, middle priority. (Please no other values here)

Changes: the code. Please put here a piece of code you want to simplify or improve. You’re free to fork QCObjects for your own needs but I highly recommend you to spend some time standardizing. We review everything and test everything almost everywhere we can before to put in action a code change. And it’s because we want to make QCObjects a really professional tool, not just another β€œJavaScript something”. We want your projects to be listed in the best quality line lists. So please let us reject some proposals in order to make this happen. Thanks

============

Issues will not be deleted unless they not meet the GitHub code of conduct.

All the issues will be answered as soon as possible.

Please try to read the issues first before to put a new one.

15 Cypress fails when use `should('be.visible')` on a visible element - overflow hidden with position absolute outside

Find it on GitHub

I found should('be.visible') gives wrong result sometimes (even in latest version). I finally made a simple demo to reproduce it:

index.html

```html