A README for the project helps communicate what Mindshare is and what type of activity happens in this repo. It will be helpful for others in the community to know what type of tickets to file here.
I'm not sure if there's a whole lot of detail to this one. Anything to start with will be nice, but I'd try to focus on…
Metadata Update from @jflory7: - Issue priority set to: critical (next week) - Issue set to the milestone: Fedora 28 (to May 2018) - Issue tagged with: meeting, needs feedback
This page should draw from the mindshare wiki/docs pages and be modelled on the one used by the council: <jwf> https://pagure.io/Fedora-Council/tickets/blob/master/f/README.md
This becomes an easyfix task on March 17, 2018
Metadata Update from @bex: - Issue untagged with: meeting, needs feedback - Issue assigned to x3mboy
Metadata Update from @bex: - Assignee reset - Issue priority set to: None (was: critical (next week)) - Issue tagged with: easyfix
I've created the PR #10. Please review it and comment
For some reason, I can't view the PR. I open the PR and it redirects me to the root page for the repo.
Any ideas?
<img alt="Screenshot-2018-3-19_Overview_-_mindshare_-_Pagure.png" src="/mindshare/issue/raw/files/1625ba554aa96d4054dfac43f13185f71cf00facee68bb83df7674ce002db7be-Screenshot-2018-3-19_Overview_-_mindshare_-_Pagure.png" />
Mmmm good point. I get the same message. Is this a problem in my side?
While this is solved, the README.md file can be viewed in my fork
Well, the message is well explanatory: There is no master (or any) branch in the Mindshare Pagure:
<img alt="Screenshot-2018-3-19_Overview_-_mindshare_-_Pagure.png" src="/mindshare/issue/raw/files/77923b18a7976c3e431d76fb43ad1979ffaebcf4f464d8fbcf3c7ddc873d161e-Screenshot-2018-3-19_Overview_-_mindshare_-_Pagure.png" />
I forced a master branch into existing. @x3mboy please cancel and resubmit your PR
Done!
done :)
Metadata Update from @bex: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.