This repository was archived by the owner on Apr 12, 2024. It is now read-only.
chore(*): make some files non-executable#15339
Closed
mgol wants to merge 1 commit into
Closed
Conversation
The repository contained JS/HTML/PNG files that had the executable bit enabled for no real reason.
Contributor
|
LGTM - please merge |
ellimist
pushed a commit
to ellimist/angular.js
that referenced
this pull request
Mar 15, 2017
The repository contained JS/HTML/PNG files that had the executable bit enabled for no real reason. Closes angular#15339
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore
What is the current behavior? (You can also link to an open issue here)
The repository contains JS/HTML/PNG files that had the executable bit enabled
for no real reason.
What is the new behavior (if this is a feature change)?
The files are no longer executable.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements
Other information: