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 CONTRIBUTING.md (cherry-pick #2263 into 5.0) #2273

Merged
merged 1 commit into from
Aug 16, 2016

Conversation

dedemorton
Copy link
Contributor

No description provided.

@dedemorton
Copy link
Contributor Author

@elastic/beats I figured it wouldn't hurt to cherry-pick this into 5.0. However, I'm not going to bother cherry-picking into earlier releases (unless you tell me to) because I figure most people will/should be looking at this file in master anyhow, right?

@@ -70,13 +67,13 @@ Packetbeat:
$ cd beats/packetbeat
$ make

Some of the Beats might have extra development requirements, in which case a
CONTRIBUTING.md file is find in the Beat directory.
Some of the Beats might have extra development requirements, in which case you'll find a
Copy link
Collaborator

Choose a reason for hiding this comment

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

As packetbeat is the only one with a local file, we should probably remove it in the future and here link to a general developer guide which then links to packetbeat dev guide. This again points in the direction that all dev guide should leave in on place (@urso ;-) ).

@ruflin ruflin merged commit d491fc3 into elastic:5.0 Aug 16, 2016
@ruflin
Copy link
Collaborator

ruflin commented Aug 16, 2016

@dedemorton I think we don't need to backport these kind of changes to any of the branches as it is very rare that someone looks at a branch for contribution notes I would assume.

Ofir-Lapid added a commit to build-security/beats that referenced this pull request Nov 23, 2021
…ator-parser-#2273

Feature/adding tests evaluator parser elastic#2273
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants