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

Github SignUp/SignIn

Open
#1,373 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
authentication, frontend

Research direction

Start with the existing GitHub connect button on the user integration page, then trace the signup and login pages and the GitHub route. Review how the route updates the store and session, including the persisted redirected-from route, and check the linked API issue for the server-side behavior. Done means GitHub signup and sign-in buttons work and successful authentication redirects to the original destination.

Written by the indexing model from the issue text.

Description

needs estimate

Problem

We want to add github signup/sign in in addition to the github connect we currently have.

This can be done followingly

First, we add buttons to the UI

  • Add a signup with github button to the signup page. This is basically the connect with github button on the user integration page, just with different test
  • Add a sign in with github button to the login page, same as above

Considering the behavior of the button is about the same, we should rename the existing component and then rewrite it so it yields to content (so we can specify text/content ourselves).

Next, we modify our github route

Right now, it sends the code and the state to our API and pushes the returned user into the store.

We should modify this so it also signs the returned user into the session and, if that happens, does not redirect to the settings.integrations route and instead redirects to the redirected from route (should be persisted in the session).

That's it on ember

That should be all there is to it on the side of ember. We can expand later, by, for example, allowing users who signed up through github, to set their password, etc.

The rest is done on the API - https://github.com/code-corps/code-corps-api/issues/9#issuecomment-329185148

@JoshSmith Does this sound like it should be it, or am I missing something?

Dominant language
JavaScript
Stars
120
Forks
75
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.