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

Add ManUp.js w/ git auto-update #273

Closed
wants to merge 4 commits into from
Closed

Add ManUp.js w/ git auto-update #273

wants to merge 4 commits into from

Conversation

aravindvnair99
Copy link

Resolves #272

Resolves #272

Signed-off-by: Aravind V Nair <22199259+aravindvnair99@users.noreply.github.com>
@aravindvnair99
Copy link
Author

@MattIPv4 CI says no version found on npm although I specified as git and not npm. Is it because there isn't a tag or release yet in the GitHub repository?

packages/m/ManUp.js.json Outdated Show resolved Hide resolved
"license": "Apache-2.0",
"autoupdate": {
"source": "git",
"target": "git://github.com/boyofgreen/ManUp.js.git",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repository has no tags in it, so we cannot pull any versioned files. Releases need to be tagged before we can use this as an autoupdate source.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh, yes... Thanks for the info. Is autoupdate a compulsory attribute? Because then I could remove that as judging by what ManUp.js is for, I don't think there would be an update anytime soon as HTML meta tags don't change frequently? Else, I guess I have to contact the owner of the repository to add a tag or release.

Also, shouldn't it be saying no version found on git instead of no version found on npm?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, auto-update is a required attribute, otherwise, we would have no way to add versioned files to the library.

(I've tracked the CI wording error in #275)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, thanks! Let me try contacting the owner in that case. Will close this PR and the related issue if the owner doesn't respond.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me, thank you :)

packages/m/ManUp.js.json Outdated Show resolved Hide resolved
packages/m/ManUp.js.json Outdated Show resolved Hide resolved
aravindvnair99 and others added 3 commits June 20, 2020 16:14
Co-authored-by: Matt (IPv4) Cowley <me@mattcowley.co.uk>
Co-authored-by: Matt (IPv4) Cowley <me@mattcowley.co.uk>
Co-authored-by: Matt (IPv4) Cowley <me@mattcowley.co.uk>
@MattIPv4
Copy link
Member

MattIPv4 commented Jul 2, 2020

Hey @aravindvnair99,

It looks like there hasn't been any progress here so far?
I think if nothing changes we'll want to close this PR in a couple of days time (two weeks after opening), what do you think?

@aravindvnair99
Copy link
Author

Hey @aravindvnair99,

It looks like there hasn't been any progress here so far?
I think if nothing changes we'll want to close this PR in a couple of days time (two weeks after opening), what do you think?

@MattIPv4 Yes, I agree with you. If @boyofgreen or @radiovisual don't respond, I shall close the issue tracker and pull request by this weekend.

@radiovisual
Copy link

Yes, I agree with you. If @boyofgreen or @radiovisual don't respond, I shall close the issue tracker and pull request by this weekend.

Why was I tagged in this thread? Was it a mistake, or am I missing something?

@aravindvnair99
Copy link
Author

Yes, I agree with you. If @boyofgreen or @radiovisual don't respond, I shall close the issue tracker and pull request by this weekend.

Why was I tagged in this thread? Was it a mistake, or am I missing something?

@radiovisual That's in reference to boyofgreen/ManUp.js#11. I'm sorry if I wasn't supposed to tag you. I assumed you and @boyofgreen are the authors of ManUp.js after seeing the contributors list

@radiovisual
Copy link

I assumed you and @boyofgreen are the authors of ManUp.js after seeing the contributors list

No, I only ever sent in a single PR to fix the documentation. So I wouldn't be able to help with this problem.

@aravindvnair99
Copy link
Author

I assumed you and @boyofgreen are the authors of ManUp.js after seeing the contributors list

No, I only ever sent in a single PR to fix the documentation. So I wouldn't be able to help with this problem.

@radiovisual My apologies for tagging you. Sorry for the inconvenience caused by my assumption. Have a great day! :)

@MattIPv4
Copy link
Member

MattIPv4 commented Jul 4, 2020

As there has still been no progress, I am going to close this PR. Please open a new PR if/when auto-update is available for this library.

@MattIPv4 MattIPv4 closed this Jul 4, 2020
@MattIPv4 MattIPv4 mentioned this pull request Jul 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add: ManUp.js
3 participants