Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explanation of the #100daysofcode challenge and #todayilearned hashtag #13

Closed
wuworkshop opened this issue Jan 24, 2016 · 3 comments
Closed
Assignees
Labels
[priority] high high-priority issues [state] closed the issue is now closed, see comments for more information

Comments

@wuworkshop
Copy link
Collaborator

An explanation of the #100daysofcode challenge and #todayilearned hashtag (currently side projects in development by @abdulhannanali and @linda… if you guys want to help let us know in #codebuddies-meta!)

@wuworkshop wuworkshop added [type] feature a new feature or significant change to site functionality [priority] high high-priority issues and removed [type] feature a new feature or significant change to site functionality labels Jan 24, 2016
@oliikit
Copy link
Collaborator

oliikit commented Oct 19, 2016

@wuworkshop I was actually thinking about this the other day. In Slack, we can add an automatic response for when someone asks. But also, we can advertise it on the site as part of how members show what they're learning/working on. I'm thinking it can be another snippet on the About page? At least for now?

@maudem maudem self-assigned this Feb 22, 2017
@maudem
Copy link
Collaborator

maudem commented Feb 22, 2017

I've never contributed before and I thought this would be a good place to start.

@lpatmo lpatmo added [state] backlog the issue has been raised but hasn't yet been looked at, we'll get to it Waiting For Review and removed [state] backlog the issue has been raised but hasn't yet been looked at, we'll get to it labels Sep 4, 2017
@billglover
Copy link

Is this issue still open? It is tagged as needs code review but unclear what code needs to be reviewed.

@lpatmo lpatmo closed this as completed Feb 24, 2019
@lpatmo lpatmo added the [state] closed the issue is now closed, see comments for more information label Feb 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[priority] high high-priority issues [state] closed the issue is now closed, see comments for more information
Projects
CB community
Ideas & discussions
Development

No branches or pull requests

5 participants