Closed reneeotten closed 4 years ago
Yes, definitely.
I just put my name there because this was part of the initial template proof-of-concept which I did back in February during a short hacking session. It makes no sense to keep my contact there, using MacPorts is more meaningful.
It makes no sense to keep my contact there, using MacPorts is more meaningful.
Do you have any suggestions about what would be a good e-mail address to add here instead of yours? I was thinking about the devel
list, but it's a bit inconvenient that one would need to subscribe first...
Merging #65 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #65 +/- ##
=======================================
Coverage 90.62% 90.62%
=======================================
Files 1 1
Lines 192 192
Branches 15 15
=======================================
Hits 174 174
Misses 16 16
Partials 2 2
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 32773a5...b51fcf9. Read the comment docs.
Why do you need an email address? URL should be sufficient and if not, macports-devel sounds reasonable.
Why do you need an email address? URL should be sufficient and if not, macports-devel sounds reasonable.
If you supply an author
, the author_email
is required - I've already added "macports-devel"
This PR makes the following changes:
author
field to "The MacPorts Project" (@mojca are you okay with that?). I am not sure what e-mail address to use, suggestions are welcome.url
to the GitHub pagemacports-base