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

Renamed NewCollection to NeedsTriageCollection #1202

Merged
merged 1 commit into from
Oct 25, 2016

Conversation

haseebgit
Copy link
Member

Copy link
Member

@miketaylr miketaylr left a comment

Choose a reason for hiding this comment

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

Can you make the changes consistent in the other places where NewFoo was used?

Thanks!

@@ -5,7 +5,7 @@
var diagnose = diagnose || {}; // eslint-disable-line no-use-before-define
var issues = issues || {}; // eslint-disable-line no-use-before-define

diagnose.NewCollection = Backbone.Collection.extend({
diagnose.NeedsTriageCollection = Backbone.Collection.extend({
model: issues.Issue,
url: '/api/issues/category/needstriage'
});

This comment was marked as abuse.

@miketaylr
Copy link
Member

Can you also update the commit message according to the contribution guidelines?

https://github.com/webcompat/webcompat.com/blob/master/CONTRIBUTING.md#submission-guidelines

Thanks!

@miketaylr
Copy link
Member

@haseebgit let me know if you need any help with this! ❤️

@haseebgit
Copy link
Member Author

@miketaylr I have some doubts, I will ping you on IRC

@miketaylr
Copy link
Member

@miketaylr I have some doubts, I will ping you on IRC

Sure thing, feel free to ask questions here in the issue as well.

@haseebgit
Copy link
Member Author

@miketaylr i edited this through web and now finding it difficult to update the PR, should i delete this branch and create new PR from my machine?

@miketaylr
Copy link
Member

@haseebgit as long as you're editing the files on the "patch-1" branch, it should be possible from the web (and should automatically update the PR).

(But it might be good to make edits locally, to verify that it still works after you make the changes. Let me know if you need help getting it running.)

@haseebgit
Copy link
Member Author

@miketaylr r?
there were many errors locally with git, edited on web.
I will follow proper guidelines for next patch :)

@@ -2,7 +2,7 @@
<div class="wc-UIContent">
<h2 class="wc-Title wc-Title--l">Latest Untriaged Issues</h2>
<div id="js-lastIssue">
<script type="text/template" id="new-tmpl">
<script type="text/template" id="needstriage-tmpl">
<% if (newIssues.length) { %>

This comment was marked as abuse.

This comment was marked as abuse.

@miketaylr
Copy link
Member

miketaylr commented Oct 25, 2016

@haseebgit check out this article on syncing your fork with upstream, your current repo is out of date: https://help.github.com/articles/syncing-a-fork/

@miketaylr miketaylr merged commit 25c6fb1 into webcompat:master Oct 25, 2016
@miketaylr
Copy link
Member

Thanks!

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.

2 participants