dapperargentina / goodfirstticket Goto Github PK

View Code? Open in Web Editor NEW

4.0 4.0 19.0 1.67 MB

JavaScript 60.30% HTML 0.18% CSS 39.05% PLpgSQL 0.26% Shell 0.21%

goodfirstticket's People

Contributors

Stargazers

Watchers

Forkers

colinwhitmarsh danielsunkim megaohms vcipriani acrobatic-spork photogenic-wound profoundmongoose sahilrawat001 muraliprasanth2

goodfirstticket's Issues

game-ify the app -- level-up number of commits?

Add labels and body to issue card

Sort based on created_at

nav col w/ 3 min. dead links: "tickets, resources, repo view"

Displaying issues on RepoProfile view

Create API endpoints for db data

List Of Repos view w/corresponding search bar

The overall idea here is that we have a page that helps people search through a list of repos which contain beginner tickets. There would be one row/item for each repo. Maybe we provide some stats on each repo - # of beginner tickets, # of PRs merged, # of contributors, # of stars, etc.

create client App component

Replace language with symbols/icons on issue cards

Feature to favorite issues for later

create client TicketListEntry view

Make sure server always runs in prod

We need to use forever or something to make sure server.js is always running

ticket search bar

On repo profile link to org on github (front-end fix)

Solve API throttling and job scheduling

add language dropdown to issue search

The githubWorker getIssues already accepts a string language paramter so this shouldn't be too hard

Capitalize the navbar links and remove repoProfile link

chat / forum

Add styling to views

Add language and stuff to /api/issue

We need to add the repo language and maybe other things to the issues response

'Subscribe' to ticket from our app (needs Oauth)

Use "Ticket" consistently throughout front-end

Create background job to update repos

Deploy live app

test

suggested label search

Create database schema

Route to repo profile from issues

Testtt

create client TicketList View

Figure out react routing (ie. react-router)

We are going to have multiple views/routes on our SPA. How the hell do we use react-router to swap out views? Let's discuss what the routes are before starting.

Route to resources component

wrap search bar and ticket view in 'main view component'

Delete bootstrap and other unused files

Weekly Email Of Issues

Weekly reminder of beginner issues. We should probably use https://www.mailgun.com/ or something to handle sending the email. Its API looks pretty easy.

W/o knowing much about mailgun, I think our initial goal for this should be:

1.)  a function which accepts an email address, subject line and html body and sends an email w/ those paramters.

2.)  a function which accepts a list of issues and generates an HTML email body of the issues.

Update individual repo card

-Replace date with hours since last update
-Replace words w/logos
-Add upvote, downvote, data and posts

Fix language dropdown in issue search

Fix scrolling to work anywhere on page

Add watchers_count and other info to RepoProfile card

create GET request worker that returns a list of github tickets

create user oath based on github login

create a live-search bar

Create background job to update issues

Invididual Repo Page Profile

This would be a page that displays information on a specific repo. Maybe it contains the following.
-Repo description
-Link to github repo
-Same metrics as the list repo view (stars, contribs, recent PRs, etc)
-User comments or tips on how to get started, understand the repo?