mozilla / addons-pm Goto Github PK

There have been updates to the enzyme monorepo:

• • The devDependency enzyme was updated from 3.7.0 to 3.8.0.

• The devDependency enzyme-adapter-react-16 was updated from 1.7.0 to 1.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the enzyme group definition.

enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency bootstrap was updated from 4.1.3 to 4.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

bootstrap is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

It would be nice if you click the "open" label to see all the open issues in the that milestone for example on GH. This would then make it easy to move all those issue to the next milestone in one go.

Depends on a cross repo search though so that would need testing first.

In the milestone view, the table headers could always stay visible when scrolling (like the global navigation that shows "Next", "Previous").

The /milestones/latest/ url is convenient, but it will be nice to update to the actual date based url once calculated.

The code manager repo should be added to the contribution queries.

The devDependency fetch-mock was updated from 7.2.5 to 7.2.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

fetch-mock is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

There have been updates to the react monorepo:

• • The dependency react was updated from 16.6.3 to 16.7.0.

• The dependency react-dom was updated from 16.6.3 to 16.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

This should take into account unrelated PR references as well as multiple review entries.

Instead of using include_fields=whatever and counting the empty object you can use count_only and get a response with bug_count and just the count \o/.

It's useful during the standup to sort the milestone issues by assignee so that everyone can talk about everything what they are working on for the given week, but in the current implementation it can only sort the issues by their assignee alphabetically from a to z or z to a, so we always start with the same people.

It'd be nice if we had an option to keep grouping per assignee but make the order random (maybe determined on initial page load, staying the same for the navigation session) so keep things fresh and rotate in what order people are talking about what they are doing.

For consistency the reviewer links should open in a new tab, and will also need rel="noopener noreferrer"

The devDependency pretty-quick was updated from 1.8.0 to 1.8.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

pretty-quick is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This means you aren't left at the bottom of page when new data is loaded in.

This PR listed here: https://addons-pm.herokuapp.com/milestones/2020.02.20/?dir=asc&sort=assignee (see bottom of the table) did not show up as reviewed.

The issue is mozilla/addons-server#13497 and the PR is mozilla/addons-server#13498

Looks like this is because the PR description has Fix #num rather than Fixes #num.

The devDependency node-sass was updated from 4.10.0 to 4.11.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-sass is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

At the moment creating fixtures is a very manual process. This could be automated with a script to write out the API response for a given URL.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

If we had a query parameter that would let amo-milestones filter out opened issues, we could then get a link that shows everything that was pushed for a given milestone, more or less.

@andymckay pointed out on IRC that it would be a nice link to include in the push emails we sent, perhaps more useful for some than the raw list of commits that we have in the etherpad.

The dependency graphql-tag was updated from 2.10.0 to 2.10.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

graphql-tag is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

The dependency react-scripts was updated from 2.1.1 to 2.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-scripts is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

npm install --save --save-exact [email protected]

yarn add --exact [email protected]

Your Greenkeeper Bot 🌴

The dependency react-timeago was updated from 4.1.9 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-timeago is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

This project needs a GH_TOKEN environment variable set for the server. If we start the app without it, API calls will fail.

We should mention the need for a GH_TOKEN env var with the following scopes:

public_repo, read:org

One can generate a token here: https://github.com/settings/tokens

Now that contributors can be assigned, we should filter them out from milestones into a separate list

There have been updates to the enzyme monorepo:

• • The devDependency enzyme was updated from 3.6.0 to 3.7.0.

• The devDependency enzyme-adapter-react-16 was updated from 1.7.0 to 1.7.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the enzyme group definition.

enzyme is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Currently we're using a lot of labels to figure out things like mentee assignment etc. If there's a way to derive this from the data in the bug (or assignment we should do that).

It would be great to include good-first-issues from Extension Workshop in the Contributions section!

Rather than having to choose to look at a quarters, maybe the projects page could be simplified to generate nav in a similar way to how the milestones page works.

Now that contributors can be assigned let's reflect that.

Currently the sorting for the reviewers column doesn't work.

Engineer username should be lower-cased in the links.

Could we add web-ext good-first-bugs to the Contributions panel of the Addons PM for greater visibility?

Via @wagnerand

• Go to https://addons-pm.herokuapp.com/contrib/good-first-bugs/ and click on "Good first bugs" in the header again.
• Suddenly, "Good first bugs" and "Contrib welcome" are selected.
• Similar for the https://addons-pm.herokuapp.com/contrib/contrib-welcome/ .

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

E.g: /2018/

This should be a navigation with the quarters for that year.

Right now we're loading the data all in one go, it would be nicer to split this up.

To run the tests...

The dependency apollo-boost was updated from 0.1.22 to 0.1.23.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

apollo-boost is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency graphql was updated from 14.0.2 to 14.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

graphql is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Once modified the next/prev and current milestone links should all reflect the query string changes.

The contrib queries share a lot of boilerplate. This could be reduced to one query with params for the changes.

Large screen:

Smaller screen:

Ideally this should all work relative to viewport like the circle sizes do.

The dependency @githubprimer/octicons-react was updated from 8.1.3 to 8.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@githubprimer/octicons-react is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Product: Firefox
Component: Extension Compatibility

The devDependency sinon was updated from 7.2.2 to 7.2.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

An issue number is easier to use during discussions.

Use prettier

Node 12 is now LTS, let's remove 8 and add node 12 for testing.