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

update website release ticker via cms #1144

Merged
merged 1 commit into from
Mar 4, 2018
Merged

Conversation

erquhart
Copy link
Contributor

No description provided.

@verythorough
Copy link
Contributor

verythorough commented Feb 28, 2018

Deploy preview for netlify-cms-www ready!

Built with commit ab6c8a3

https://deploy-preview-1144--netlify-cms-www.netlify.com

@verythorough
Copy link
Contributor

verythorough commented Feb 28, 2018

Deploy preview for cms-demo ready!

Built with commit ab6c8a3

https://deploy-preview-1144--cms-demo.netlify.com

@@ -36,7 +36,7 @@ <h3>{{ .feature | markdownify }}</h3>
<ol>
{{ range .Site.Data.updates }}
{{ range first 3 . }}
<a href="{{ .url }}"><li><div class="update-metadata"><span class="update-version">{{ .version }}</span><span class="update-date">{{ dateFormat "January 2, 2006" .date }}</span></div><span class="update-description">{{ .description | markdownify }}</span></li></a>
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not just use the url from the updates.yml?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's what this is - Site.Data.updates is read in from the yaml.

Copy link
Contributor

Choose a reason for hiding this comment

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

It was changed from {{ .url }} to https://github.com/netlify/netlify-cms/releases/tag/{{ .version }}. We still have the URL in the Site.Data.updates, though, why not just use that url?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, sorry, should have looked closer.

We're going to drop the urls entirely - that way we don't have to manually enter a url every time, just derive it using the version. Not sure why I didn't drop them.

@erquhart erquhart force-pushed the website-releases-cms-config branch from d785aaa to ab6c8a3 Compare March 2, 2018 21:47
Copy link
Contributor

@tech4him1 tech4him1 left a comment

Choose a reason for hiding this comment

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

LGTM. It would be cool if we could automatically pull this data GitHub.

@erquhart
Copy link
Contributor Author

erquhart commented Mar 2, 2018

Agreed.

@erquhart
Copy link
Contributor Author

erquhart commented Mar 2, 2018

Merge after #1143, otherwise date formats will be wrong.

@erquhart erquhart merged commit 53490f7 into master Mar 4, 2018
@erquhart erquhart deleted the website-releases-cms-config branch March 4, 2018 03:56
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.

3 participants