Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Some files should be removed

Open
#5 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Stale
Tech stack
coffeescript, rails, ruby, scss
Domain
tooling

Research direction

Start by checking the listed helper files, CoffeeScript assets, and SCSS stylesheets to confirm they are empty and unused. Remove the listed files and verify that the application still works without them; completion means the empty files are gone without breaking the app.

Written by the indexing model from the issue text.

Description

Thank you for the app! It helps very much!
Still there's a lot of empty files which just confuse people (at least me). I suggest removing these files to make the app cleaner and it would be taking less time to look through.

Here's the list of such files:

- helpers:
feeds_helper.rb
folows_helper.rb
items_helper.rb
landing_helper.rb
pins_helper.rb

- assets:
feeds.js.coffee
folows.js.coffee
items.js.coffee
landing.js.coffee
pins.js.coffee

- stylesheets:
feeds.css.scss
folows.css.scss
items.css.scss
landing.css.scss
pins.css.scss

Dominant language
Ruby
Stars
38
Forks
26
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GetStream/Stream-Example-Rails

All issues in GetStream/Stream-Example-Rails

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.