-
Notifications
You must be signed in to change notification settings - Fork 144
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
Automate posting project releases to aboutcode.org #122
Comments
@mjherzog,plzz assign me, i would like to contribute in your issue. |
Hi @mjherzog , I would like to contribute to this issue |
Hey is the issue solved ? otherwise i would like to contribute |
IS this issue still active? can i contribute? |
Could you please assign this issue to me? |
@poju3185 We do not "assign" issues, so if none else chimes here stating they are actively working on it, you are welcome to go for it. Please make sure to explain your approach here first and to report your progress here on a regular basis as comments. |
Got it! Just that recently, I often encounter situations where, after I submit a PR, someone will make slight modifications to my PR and then submit another PR. |
This would be a totally UNACCEPTABLE behavior in our projects, so no need to worry about this. |
@poju3185 I meant to say:
|
Ahh, that makes much more sense, thanks for the clarification :) |
We need to automate posting project releases to the News feed on aboutcode.org. Aboutcode.org is the primary website for information about any and all of our many projects so it would be a good place to post project releases so that a viewer can see consolidated information across projects.
The idea is to create a News template that would be a requirement for any release. The information should be very simple with a simple title like "Project version x.y.z released" with links to the Releases page for each project.
We already seem to have a basic template as with https://www.aboutcode.org/news/2021-12-17-scancode.io.html, but the posting process is manual.
The text was updated successfully, but these errors were encountered: