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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap up @tnir's contributions at forem (Early 2022) #17645
Comments
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you. Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev. To our amazing contributors: issues labeled To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up. For full info on how to contribute, please check out our contributors guide. |
forem/forem-docs#82 might be merged in the near future. However forem/forem-docs#74 will be hard... |
forem/forem-docs#82 was just merged. forem/forem-docs#74 would be the very last part of this issue. |
With https://dev.to/devteam/dev-team-update-261j, now it looks like less resources to complete some ongoing tasks. Closing as completed now. |
Sort out my stuffs at forem Org now 馃檹 馃憢
Starting with a single problem resolution at #16928, I enjoyed some improvements and kind review feedbacks to a new product born in 2017 (while the initial commit at GitHub looks like 301c608).
forem (Rails/React app)
forem-docs
Pending
forem (Rails/React app)
Merged 馃槍
https://github.com/forem/forem/pulls/tnir?q=is:merged
forem-docs
Merged 馃槍
https://github.com/forem/forem-docs/pulls/tnir?q=is:merged
The text was updated successfully, but these errors were encountered: